Engineering the Future of Software
April 2–3, 2017: Training
April 3–5, 2017: Tutorials & Conference
New York, NY

Three rules for domain-driven design

Steven Lowe (Google)
1:15pm–2:05pm Wednesday, April 5, 2017
Location: Sutton South/Regent Parlor
Level: Intermediate
Average rating: ****.
(4.67, 6 ratings)

Who is this presentation for?

  • Developers, business analysts, Scrum masters, and consultants

Prerequisite knowledge

  • Basic familiarity with Agile practices
  • Software development knowledge and experience

What you'll learn

  • Understand where and how to apply just enough DDD, just in time, to ensure that your overall design evolves in a coherent fashion


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.

Photo of Steven Lowe

Steven Lowe


Steven Lowe writes science fiction software music and leaves out commas. He’s the author of Head-First Domain-Driven Design for O’Reilly.