InfoQ Homepage Patterns Content on InfoQ
-
/articles/CSharp-Models/en/smallimage/net-logo-1526676504145.jpeg)
Models and Their Interfaces in C# API Design
Traditional MVC, MVP, MVVM, Web MVC; the common element in every UI pattern is the Model. And while there are many articles discussing the view, controllers, and presenters in these architectures, almost no thought is given to the models. In this article we’ll look at the model itself and the .NET interfaces that they implement.
-
/articles/cloud-native-panel/en/smallimage/cloud-logo-1508587932376.jpeg)
Defining Cloud Native: A Panel Discussion
What is "cloud-native", why should you care, and how can your team adopt this way of delivering software? InfoQ gathered three industry experts to debate the topic.
-
/articles/book-review-rise-software-recipes/en/smallimage/cover.jpg)
Q&A on The Rise and Fall of Software Recipes
Darius Blasband has written a book which challenges the conventional wisdom of software engineering: he protests against the adoption of recipes and standards-based approaches and rails against the status-quo. He calls himself a codeaholic who advocates for careful consideration of the specific context and the use of domain specific languages wherever possible.
-
/articles/repository-advanced/en/smallimage/net-logo.jpg)
Advanced Use Cases for the Repository Pattern in .NET
In our previous article, we looked at the basic patterns needed to implement a repository. In many cases these patterns were such a thin layer around the underlying data access technology they were essentially unnecessary. However, once you have a repository in place, many new opportunities become available.
-
/articles/repository-implementation-strategies/en/smallimage/logo-net.jpg)
Implementation Strategies for the Repository Pattern with Entity Framework, Dapper, and Chain
This article will focus on the basic functionality that one would find in a typical repository created with .NET. We’ll look at both general functionality and how that functionality would be implemented using three different styles of ORM: Entity Framework, Dapper, and Tortuga Chain.
-
/articles/integration-mistakes/en/smallimage/pamod-logo.jpg)
Two Mistakes You Need to Avoid When Integrating Services
With SOA, businesses moved from monolithic applications to heterogeneous designs by decomposing functionality into services. However, architects must be careful when integrating services. Often enterprises assume adopting patterns like ESB can help. Unfortunately, there are hidden challenges with these patterns. The danger is they go unnoticed during development but surface when a system is live.
-
/articles/continuous-delivery-coding-patterns/en/smallimage/logo.jpg)
Continuous Delivery Coding Patterns: Latent-to-Live Code & Forward Compatible Interim Versions
This article describes two novel practices for continuous delivery: Latent-to-live code pattern and Forward compatible interim versions. You can use these practices to simultaneously increase speed and reliability of software development and reduce risks. These practices are built on top of two other essential continuous delivery practices: trunk-based-development and feature toggles.
-
/articles/Apache-Tamaya-Configure-Once-Run-Everywhere/en/smallimage/java-logo.jpg)
Configure Once, Run Everywhere: Decoupling Configuration and Runtime
Configuration is one of the most widely used cross-cutting concerns in application development. Apache Tamaya is a new incubator project that brings standardized property management to Java.
-
/articles/reactive-messaging-patterns-with-actor-model-book-review/en/smallimage/ShowCover (1).jpg)
Reactive Messaging Patterns with the Actor Model Book Review and Q&A with Vaughn Vernon
Vaughn Vernon in his new book Reactive Messaging Patterns with the Actor Model shows how this model can simplify enterprise software development. After an introduction to the basics of the actor model and tutorials on Scala and Akka the rest of the book is a patterns catalogue describing most of the patterns in the book Enterprise Integration Patterns from an actor model perspective.
-
/articles/patterns-devops-culture/en/smallimage/series-logo.jpg)
Article Series: Patterns of DevOps Culture
Healthy organizations exhibit similar patterns of behavior, organization and improvement efforts. In this series we explore some of those patterns through testimonies from their practitioners and through analysis by consultants in the field who have been exposed to multiple DevOps adoption initiatives.
-
/articles/devops-team-topologies/en/smallimage/topologies-DevOps-logo-1528887456050.jpg)
How Different Team Topologies Influence DevOps Culture
There are many different team topologies that can be effective for DevOps. Each topology comes with a slightly different culture, and a team topology suitable for one organisation may not be suited to another organisation, even in a similar sector. This article explores the cultural differences between team topologies for DevOps, to help you choose a suitable DevOps topology for your organisation.
-
/articles/seven-uservices-antipatterns/en/smallimage/logoSmall.jpg)
Seven Microservices Anti-patterns
In this article Vijay Algarasan, a Principal Architect at Asurion, discusses how he and his teams have encountered microservices at various engagements and some lessons they have learned as a result. This has resulted in them building up a series of anti-patterns and some associated patterns, which Vijay believes are more widely applicable to all practitioners of microservices