Table of Contents
Preface
Part 1: Foundations
Chapter 1: The Rationale for Domain-Driven Design
Why do software projects fail?
Inaccurate requirements
Too much architecture
Too little architecture
Excessive incidental complexity
Uncontrolled technical debt
Ignoring non-functional requirements
Modern systems and dealing with complexity
How software gets built
Complexity is inevitable
Optimizing the feedback loop
What is DDD?
Understanding the problem using strategic design
Promoting a shared understanding using a ubiquitous language
Implementing the solution using tactical design
Why is DDD relevant? Why now?
Rise of open source
Advances in technology
Rise of distributed computing
Summary
Further reading
Chapter 2: Where and How Does DDD Fit? ...
Get Domain-Driven Design with Java - A Practitioner’s Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
