Three rules for domain-driven design

Domain-driven design (DDD) helps focus and guide software development efforts, but learning DDD can be a daunting task. Steven Lowe shares three simple philosophical rules that guide understanding and application of DDDcapture the domain model, embed it in the code, and protect it from corruptionand explains how these rules guide DDD at all scales.

The key to a successful DDD project is the concept of “harmonious models”—that the model in the code matches the way the business thinks and talks about how it works. This alignment is what allows the software to adapt to changes in the business without breaking. It also enables insights about the business, both for developers and stakeholders. Steven Lowe shares three simple philosophical rules that guide understanding and application of DDD—capture the domain model, embed it in the code, and protect it from corruption—and explains how these rules guide DDD at all scales. DDD is deep and broad, but you don’t necessarily need all of it all of the time. These three guidelines help you decide how much DDD to use and when and where to use it.