InfoQ Homepage Domain Driven Design Content on InfoQ
-
/articles/refactoring-deeper-model/en/smallimage/refactoring-deeper-model-logo-small-1535981170078.jpg)
Refactoring to a Deeper Model
Paul Rayner uses a case study to demonstrate how refactoring your code can lead to a deeper understanding of your domain model. Through common code refactorings, combined with the implementation of patterns, the codebase became more cohesive and easier to reason about, reducing the time to perform some common tasks from weeks or months to just hours.
-
/articles/ddd-with-tlc/en/smallimage/ddd-with-tlc-1535156092540.jpg)
DDD With TLC
At the 2017 Explore DDD conference, Julie Lerman, a self-described Serial DDD Advocate, spoke about how to approach Domain-Driven Design with Tender Loving Care. InfoQ sat down with Lerman to ask about how she introduces DDD to new clients, and helps them be successful.
-
/articles/soa-microservices-journey/en/smallimage/SOA-to-Microservices-1529490054149.jpeg)
The SOA Journey: from Understanding Business to Agile Architecture
If your monolith is tightly coupled and not cohesive, you could split it in order for a business to be more agile. There are a lot of wrong ways that you can do that. They result in the same tightly coupled and non-cohesive monolith, but which is distributed across a network. This article examines how you can align your technical services and business-capabilities.
-
/articles/Microservices-Architectural-Fitness/en/smallimage/logo-java.jpeg)
Perspective on Architectural Fitness of Microservices
In this article we peel the onion of potential architectural fitness of microservices in the context of Master Data Management, and the challenges a microservices-based architecture may face when solving problem domains that require compute-intensive tasks, such as the calculation of expected losses on a portfolio of unsecured consumer credit.
-
/articles/scs-microservices-done-right/en/smallimage/GettyImages-517987828.jpg)
Self Contained Systems (SCS): Microservices Done Right
Everybody seems to be building microservices these days. There are many different ways to split a system into microservices, and there appears to be little agreement about what microservices actually are - except for the fact that they can be deployed independently. Self-contained Systems are one approach that has been used by a large number of projects.
-
/articles/microservices-aggregates-events-cqrs-part-2-richardson/en/smallimage/logo-cqrs.jpg)
Developing Transactional Microservices Using Aggregates, Event Sourcing and CQRS - Part 2
This article concludes the description of a way to develop microservices using Domain Driven Design, Event Sourcing and Command Query Responsibility Segregation (CQRS). The practical considerations and benefits of this approach are compared with other options.
-
/articles/microservices-aggregates-events-cqrs-part-1-richardson/en/smallimage/logo-cqrs.jpg)
Developing Transactional Microservices Using Aggregates, Event Sourcing and CQRS - Part 1
Developing transactional business applications using the microservice architecture is challenging, because domain models, transactions and queries are resistant to functional decomposition. This article describes a way to develop microservices that solves these problems by using Domain Driven Design, Event Sourcing and Command Query Responsibility Segregation (CQRS).
-
/articles/cqrs-business-kaminski/en/smallimage/logo.jpg)
CQRS for Enterprise Web Development: What's in it for Business?
With a focus on the business case for a CQRS architecture, this article covers the core concepts of Command Query Responsibility Segregation, and contrasts them with a common, n-tier architecture. Benefits including scalability and maintainability are highlighted, which can reduce the total cost of ownership, and lead to an improved return on investment when choosing a CQRS architecture.
-
/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/implmenting-domain-driven-design-vaughn-vernon/en/smallimage/logo.jpg)
There is a Cowboy in my Domain! - Implementing Domain Driven Design Review and Interview
Implementing Domain Driven Design, has brought clarity to an important but little understood area of software design. As a measure of Software Design literature, Vaughn's work is educational and fun. With real world code samples and sage advice, IDDD guides the reader through the sometimes murky waters of DDD and helps them gain the insight required to start a DDD journey of their own.
-
/articles/crosscutting-feature-design/en/smallimage/article logo.jpg)
Designing and Developing Cross-Cutting Features
Every developer has had to integrate with another system, API or component at one point or another. And, often, a business feature must span systems. If you’ve been on a project like this or have one in the pipeline then this article provides strategies to handle the change. Also, this article covers separating system boundaries and what that means for your technical design.
-
/articles/healthcare-emr-ehr/en/smallimage/health.png)
Healthy Architectures - Using CQRS and Event Sourcing for Electronic Medical Records
The health care industry has been migrating to electronic medical/health records (EMR/EHR) for some time. Hopwever, problems such as performance and scalability, along with maintaining traceability and reconstructing healthcare related business events need to be addressed. The article introduces the use of techniques and patterns for providing these quality attributes.