Domain Driven Design Books
Showing 1-42 of 42

by (shelved 28 times as domain-driven-design)
avg rating 4.15 — 5,755 ratings — published 2003

by (shelved 18 times as domain-driven-design)
avg rating 4.05 — 1,279 ratings — published 2013

by (shelved 15 times as domain-driven-design)
avg rating 4.44 — 672 ratings — published

by (shelved 11 times as domain-driven-design)
avg rating 4.36 — 384 ratings — published 2014

by (shelved 9 times as domain-driven-design)
avg rating 4.49 — 661 ratings — published

by (shelved 9 times as domain-driven-design)
avg rating 3.82 — 1,304 ratings — published

by (shelved 9 times as domain-driven-design)
avg rating 3.59 — 565 ratings — published 2006

by (shelved 4 times as domain-driven-design)
avg rating 4.01 — 84 ratings — published 2014

by (shelved 4 times as domain-driven-design)
avg rating 3.58 — 234 ratings — published 2006

by (shelved 3 times as domain-driven-design)
avg rating 3.96 — 92 ratings — published

by (shelved 2 times as domain-driven-design)
avg rating 4.33 — 3 ratings — published

by (shelved 2 times as domain-driven-design)
avg rating 3.98 — 84 ratings — published

by (shelved 2 times as domain-driven-design)
avg rating 3.57 — 7 ratings — published

by (shelved 2 times as domain-driven-design)
avg rating 4.50 — 2 ratings — published

by (shelved 2 times as domain-driven-design)
avg rating 3.96 — 27 ratings — published

by (shelved 2 times as domain-driven-design)
avg rating 4.20 — 15 ratings — published

by (shelved 2 times as domain-driven-design)
avg rating 4.22 — 5,134 ratings — published 2014

by (shelved 2 times as domain-driven-design)
avg rating 3.62 — 105 ratings — published 2014

by (shelved 1 time as domain-driven-design)
avg rating 4.20 — 168 ratings — published

by (shelved 1 time as domain-driven-design)
avg rating 4.26 — 773 ratings — published 2021

by (shelved 1 time as domain-driven-design)
avg rating 3.99 — 125 ratings — published

by (shelved 1 time as domain-driven-design)
avg rating 3.98 — 59 ratings — published 2015

by (shelved 1 time as domain-driven-design)
avg rating 3.72 — 105 ratings — published 2002

by (shelved 1 time as domain-driven-design)
avg rating 4.00 — 11 ratings — published

by (shelved 1 time as domain-driven-design)
avg rating 4.19 — 5,331 ratings — published 2019

by (shelved 1 time as domain-driven-design)
avg rating 4.10 — 267 ratings — published 2014

by (shelved 1 time as domain-driven-design)
avg rating 2.75 — 8 ratings — published

by (shelved 1 time as domain-driven-design)
avg rating 3.18 — 28 ratings — published

by (shelved 1 time as domain-driven-design)
avg rating 4.41 — 469 ratings — published

by (shelved 1 time as domain-driven-design)
avg rating 3.95 — 19 ratings — published

by (shelved 1 time as domain-driven-design)
avg rating 3.86 — 119 ratings — published

by (shelved 1 time as domain-driven-design)
avg rating 3.92 — 24 ratings — published

by (shelved 1 time as domain-driven-design)
avg rating 4.00 — 2 ratings — published

by (shelved 1 time as domain-driven-design)
avg rating 4.12 — 3,866 ratings — published 2002

by (shelved 1 time as domain-driven-design)
avg rating 4.01 — 248 ratings — published 2009

by (shelved 1 time as domain-driven-design)
avg rating 2.88 — 34 ratings — published 2013

by (shelved 1 time as domain-driven-design)
avg rating 4.00 — 2 ratings — published 2012

by (shelved 1 time as domain-driven-design)
avg rating 4.12 — 1,542 ratings — published 2003

by (shelved 1 time as domain-driven-design)
avg rating 3.85 — 274 ratings — published 1996

by (shelved 1 time as domain-driven-design)
avg rating 3.47 — 15 ratings — published 2009

by (shelved 0 times as domain-driven-design)
avg rating 4.40 — 171 ratings — published

by (shelved 0 times as domain-driven-design)
avg rating 2.00 — 1 rating — published 1999
“Domain-Driven Design (DDD) is a process that aligns your code with the reality of your problem domain.”
― Patterns Principles and Practices of Domain Driven Design
― Patterns Principles and Practices of Domain Driven Design
“One of the patterns from domain-driven design is called bounded context. Bounded contexts are used to set the logical boundaries of a domain’s solution space for better managing complexity. It’s important that teams understand which aspects, including data, they can change on their own and which are shared dependencies for which they need to coordinate with other teams to avoid breaking things. Setting boundaries helps teams and developers manage the dependencies more efficiently.
The logical boundaries are typically explicit and enforced on areas with clear and higher cohesion. These domain dependencies can sit on different levels, such as specific parts of the application, processes, associated database designs, etc. The bounded context, we can conclude, is polymorphic and can be applied to many different viewpoints. Polymorphic means that the bounded context size and shape can vary based on viewpoint and surroundings. This also means you need to be explicit when using a bounded context; otherwise it remains pretty vague.”
― Data Management at Scale: Best Practices for Enterprise Architecture
The logical boundaries are typically explicit and enforced on areas with clear and higher cohesion. These domain dependencies can sit on different levels, such as specific parts of the application, processes, associated database designs, etc. The bounded context, we can conclude, is polymorphic and can be applied to many different viewpoints. Polymorphic means that the bounded context size and shape can vary based on viewpoint and surroundings. This also means you need to be explicit when using a bounded context; otherwise it remains pretty vague.”
― Data Management at Scale: Best Practices for Enterprise Architecture