Domain-Driven Design
Get a brief overview of the domain-driven design and its misconceptions.
Domain-driven design (DDD) is a very large and complex topic, with entire books devoted to the use and implementation of the many patterns and methodologies that are brought together. We won’t try to fit all of it into this chapter, much less this section, so we’ll be taking a high-level look at the key strategic patterns that are useful to us as we design and develop event-driven applications. As for the tactical patterns, we’ll be seeing examples of their use throughout.
Going deeper into DDD
For an in-depth look at DDD, we can recommend both Domain-Driven Design: Tackling Complexity in the Heart of Software by Eric Evans as an original introduction to the topic and Implementing Domain-Driven Design by Vaughn Vernon for the expansion of the topic and a deeper dive into the strategic patterns of DDD. Finally, Patterns, Principles, and Practices of Domain-Driven Design by Scott Millett with Nick Tune round out the recommendations with its very deep and lengthy look at DDD.
DDD misconceptions
The philosophies, methodologies, and patterns of DDD are well-suited for the development of event-driven applications. Before getting into DDD, we would like to cover a couple of misconceptions about it that developers might hold.
Get hands-on with 1400+ tech skills courses.