Learning Domain-Driven Design explains how software models and architecture relate to business needs. Vlad Khononov introduces strategic and tactical DDD for developers and architects, covering subdomains, ubiquitous language, bounded contexts, aggregates, domain events, and collaborative discovery, with scenarios that connect modeling decisions to system boundaries and implementation patterns.
Digital ebook. Checkout sends an order request.
Business analysis provides the starting point for this guide to domain-driven design. Khononov explains how to distinguish core, supporting, and generic subdomains, establish a shared vocabulary, and identify bounded contexts. Context maps then describe the relationships and integration choices among different parts of a system.
Tactical discussions consider entities, value objects, aggregates, repositories, services, and domain events. The book also explores Event Storming as a collaborative way to discover domain knowledge and relates DDD ideas to architectural approaches such as microservices and event-driven systems. Developers and architects can use its scenarios to examine how business priorities influence modeling depth, boundaries, and the organization of software.
Khononov starts from business rather than code: understand the domain, divide it into subdomains, name the language and draw the boundaries. Strategic and tactical DDD then connect that analysis to aggregates, domain events and architectural choices such as microservices and event-driven systems.
Business analysis is the entry point. Khononov explains how to separate core, supporting and generic subdomains, establish a shared vocabulary and identify bounded contexts, with context maps describing how the pieces relate and integrate. Tactical material then covers entities, value objects, aggregates, repositories, services and domain events, each carrying rules about consistency and responsibility. Event Storming appears as a collaborative way to surface domain knowledge, and the closing discussion relates DDD to microservices and event-driven architecture. Developers and architects can use the scenarios to see how business priorities shape modeling depth, boundaries and the organization of software.
Domain-driven design starts by understanding what the business does. Subdomain analysis separates the work that matters most from supporting and generic activity, and that separation guides where modeling effort belongs.
A shared vocabulary is treated as a design instrument. When business and technical people use the same terms consistently, the model and the conversation stay aligned.
Bounded contexts mark where a model applies, and context maps describe relationships between them. Together they give architecture a vocabulary for boundaries and integration choices.
Entities, value objects, aggregates, repositories, services and domain events are presented as tools for expressing a model in code. Each carries rules about consistency and responsibility.
Event Storming is offered as a collaborative way to surface domain knowledge. The technique brings the people who know the business into the modeling conversation.
DDD is related to microservices and event-driven systems, with boundaries informing how a system is divided. Architecture is a consequence of domain decisions, not a starting aesthetic.
Software developers and architects who want to apply domain-driven design, from strategic business analysis through tactical patterns, to systems whose structure must reflect business priorities.
Edition, audience, and study-guide details at a glance.
Learning Domain-Driven Design explains how software models and architecture relate to business needs. Vlad Khononov introduces strategic and tactical DDD for developers and architects, covering subdomains, ubiquitous language, bounded contexts, aggregates, domain events, and collaborative discovery, with scenarios that connect modeling decisions to system boundaries and implementation patterns.
This listing is for the 1st edition. Check the title, ISBN, and book details above before ordering, especially if your course or reading list names a specific edition.
Software developers and architects who want to apply domain-driven design, from strategic business analysis through tactical patterns, to systems whose structure must reflect business priorities.
Yes. This page includes an original study guide with six thematic sections, key takeaways, and a topic map for structured reading.
More books with overlapping topics.
