57. Domain-Driven Design

Domain-Driven Design is an approach to software development, and contains a number of tactical patterns which we can use in projects with lots of business logic complexity.

Here's how it works:

  • Discover the domain model by interacting with domain experts and agreeing upon a common language to refer to processes, actors and any other important phenomenon (like events and side-effects to events) that occur in your problem domain.
  • Take those newly discovered terms and embed them in the code, creating a rich domain model that reflects the actual living, breathing business and its rules.

Howdy 👋

This is an online wiki about the main topics over the last 40 years of software design, architecture & testing. It was created by Khalil Stemmler.

This wiki's mission is to help eliminate the unknown unknowns, helping you get up to speed on the best practices and principles to write testable, flexible, and maintainable code.

I created this wiki while I was connecting the dots on my own path. You can read more about that learning journey in the introduction

Already bought it?

If you’ve already purchased the book, click here to re-send your link. You can read the online wiki or download a copy of the book in PDF, EPUB, and Kindle versions.

Want access?

You can read the intro to the book for free and visit solidbook.io to buy the book/wiki! To get an idea of my writing, read some of my best free content here and here.

Need help?

Something not working? Have a question? You can reach me on at khalil@khalilstemmler.com.