InfoQ Homepage Domain-Driven Design Content on InfoQ
-
Acknowledging CAP at the Root -- in the Domain Model
Eric Evans discusses three DDD patterns helping embedding CAP tradeoffs inside the domain model: Aggregates, Domain Events and Bounded Contexts.
-
Legacy Code: Using Domain-Driven Design to Carve Out Areas of Sanity
Robert Reppel discusses applying DDD and SOLID techniques in order to improve legacy code, exemplifying with real code.
-
Recovering the Ability to Design when Surrounded by Messy Legacy Systems
Eric Evans shares 4 strategies for dealing with messy legacy systems: Bubble Context, ACL Synchronization, Exposing Legacy Assets, and Domain Events Channel.
-
Spring Data JPA – Repositories Done Right
Oliver Gierke demoes using Spring Data JPA to create repositories using a Domain-driven Design approach.
-
Case Study: Large-scale Pure OO at the Irish Government
Richard Pawson discusses a case study of a large pure OO project for the Irish government, presenting the challenges met, the reason for choosing pure OO, and lessons learned implementing it.
-
Futures Trade Flow
Ian Bond presents the development of a trade flow event-driven architecture, providing the background of futures trade, the domain and the solution, sharing some of the lessons learned along the way.
-
RESTful SOA or Domain-Driven Design - A Compromise?
Vaughn Vernon advocates using DDD’s strategic modeling patterns when integrating services in a RESTful SOA implementation, avoiding one of SOA’s pitfalls: focusing on services rather than the domain.
-
Sustainable Design for Agile Teams
Eric Evans advocates on gradual blending of modeling and design into iterative development in an attempt to create a solution that expresses the domain and is flexible enough to support changes.
-
Power Use of Value Objects in DDD
Johnsson refreshes the listeners’ memory on using value objects showing by example how their good use can revolutionize a program’s architecture, simplifying it, making it more readable and testable.
-
Is Domain-Driven Design More than Entities and Repositories?
Jimmy Nilsson explains why DDD is different: it builds on collaboration and feedback, incorporates deep domain knowledge, having as end result: reduced complexity, testability, and maintainability.
-
Strategic Design - Responsibility Traps
Eric discusses the need for strategic thinking and how early design decisions can affect project and organization trajectories and why they involve much more than mere architecture.
-
What I've learned about DDD since the book
Eric Evans reviews what he has learned in the 5 years since the publication of Domain Driven Design. He also describes some new patterns and talks about changes of emphasis for existing patterns.