Pragmatic DDD

Domain-Driven Design without dogma: when it pays off, the four layers in Java, testing, error handling and moving an existing codebase towards a rich domain.

3 of 3 parts published

1. Part 1 of 3

   Pragmatic DDD: When It Pays Off and When It Doesn't

   When Domain-Driven Design earns its cost and when a transaction script is the better choice: a decision matrix, a path from simple to rich models, and the patterns teams overuse.

   14 Oct 2026 · 3 min read

2. Part 2 of 3

   The Four Layers of Pragmatic DDD: Code, Packages and Java 25

   Which way dependencies point, how one request crosses the layers, what belongs in each of the four layers, how they map to packages, and the Java 25 features that keep the domain model short.

   21 Oct 2026 · 4 min read

3. Part 3 of 3

   Pragmatic DDD in Practice: Testing, Errors, Migration and Pitfalls

   Fast domain tests and a few full-stack ones, exceptions that each layer translates, moving a service-heavy codebase to a rich domain step by step, and four common pitfalls.

   28 Oct 2026 · 5 min read