Awesome Domain-Driven Design 
A curated list of Domain-Driven Design (DDD), Command Query Responsibility Segregation (CQRS), Event Sourcing, and Event Storming resources.
Check out my blog and weekly DDD newsletter or say hi on Twitter!
Domain-Driven Design (DDD) is an approach to software development for complex needs by connecting the implementation to an evolving model. The premise of Domain-Driven Design is the following:
- placing the project's primary focus on the core domain and domain logic
- basing complex designs on a model of the domain
- initiating a creative collaboration between technical and domain experts to iteratively refine a conceptual model that addresses particular domain problems
The term was coined by Eric Evans in his book of the same title.
Command Query Responsibility Segregation (CQRS) is simply the creation of two objects where there was previously only one. The separation occurs based upon whether the methods are a command or a query (the same definition that is used by Meyer in Command and Query Separation, a command is any method that mutates state and a query is any method that returns a value).
Event Sourcing the fundamental idea of Event Sourcing is that of ensuring every change to the state of an application is captured in an event object, and that these event objects are themselves stored in the sequence they were applied for the same lifetime as the application state itself.
Event Storming is a workshop format for quickly exploring complex business domains.
Contents
- Awesome Domain-Driven Design
Books
- Applying Domain Driven Design with CQRS and Event Sourcing - A walkthrough of using EventStorming and other modeling techniques to build a CQRS and Event Sourcing-based prototype for a fictional business domain.
- Architecture Modernization - Concrete tools, techniques, and processes to align software architecture with your business domains, organizational design, team topologies, and corporate strategy.
- Collaborative Software Design - A practical guide for effectively involving all stakeholders in the design of software.A practical guide for effectively involving all stakeholders in the design of software.
- CQRS - Notes by Mark Nijhof from his experiences learning DDD and CQRS from Greg Young. There is an extensive sample project that accompanies this book.
- Domain-Driven Design: Tackling the Complexity at the Heart of Software - The canonical book that coined the term Domain-Driven Design. Also known as the "Blue Book."
- Domain-Driven Design Distilled - Very good starter book before you read Implementing Domain-Driven Design or Domain-Driven Design: Tackling the Complexity at the Heart of Software.
- Domain-Driven Design in PHP - Real examples written in PHP showcasing DDD Architectural Styles, Tactical Design, and Bounded Context Integration.
- Domain-Driven Rails - Domain-Driven Rails describes 11 techniques (from Bounded Contexts to Event Sourcing) that you can use separately and together in new and old Rails apps to achieve better architecture.
- Domain Modeling Made Functional - Tackle Software Complexity with Domain-Driven Design and F#.