Book
Learning Domain-Driven Design
Aligning Software Architecture and Business Strategy
Vlad Khononov
Summary
Vlad Khononov rebuilds Eric Evans' original DDD material into a more approachable, example-driven path, working through a single fictional company's domain from strategic patterns like bounded contexts and context mapping down to tactical implementation choices for simple and complex business logic. Later chapters connect DDD to microservices boundaries, event-driven architecture, and event storming as a discovery technique. It reads as an on-ramp: readers who want the deeper theoretical grounding are pointed back to Evans' original text.
Editor's Note
For those who want to first map DDD's strategic and tactical patterns at an introductory level. More approachable than the original, it gives a practical grasp of bounded contexts — an entry point, with deeper theory left to the source.
Target Readers
- Developers encountering domain-driven design for the first time who find Eric Evans' original text dense as a starting point
- Architects defining service boundaries for a microservices migration and needing a vocabulary for where one service's responsibility ends
- Teams introducing event storming or context mapping as a discovery exercise and wanting the reasoning behind the technique
Tags
Colophon
- Publisher
- O'Reilly Japan
- ISBN
- 978-4814400737
- Published
- Jul 2024
- List price
- ¥3,960incl. taxMay differ from the actual selling price on Amazon
Get this book
* The link above is an advertisement via Amazon Associates.Related Books
Prerequisites
- Recommended
Clean Architecture
A Craftsman's Guide to Software Structure and Design
Robert C. Martin
Reason: Once you can control the direction of dependencies, the next question becomes where to draw the boundaries. Domain-Driven Design derives bounded contexts from the language of the business, giving architectural decomposition real meaning.
Next Books
- Recommended
Domain-Driven Design: Tackling Complexity in the Heart of Software
Eric Evans
Reason: After mapping the strategic and tactical landscape with an introductory text, you verify the origin and precise definitions of the concepts in the source. Evans' DDD grounds the ubiquitous language and model-driven design, forming the foundation for applied judgment.
- Recommended
Team Topologies
Organizing Business and Technology Teams for Fast Flow
Matthew Skelton, Manuel Pais
Reason: Once you can draw bounded contexts, you map those boundaries onto team structure. Aligning contexts with teams lowers cognitive load and speeds the flow of value.
- Recommended
Tsukurinagara Manabu! Domain-Driven Design Jissen Nyumon (A Hands-On Practical Introduction to Domain-Driven Design)
Yuya Yamashita (supervised by Toru Masuda)
Reason: Even after getting a map of bounded contexts and strategic/tactical patterns from 'Learning Domain-Driven Design,' it's still hard to picture what to put where in your own code. 'Learning DDD Through Practice' bridges that gap by building an online bookstore in TypeScript, working through concrete decisions like referencing aggregates by ID.