- How DDD differs from other architectural approaches
- How DDD fits with agile
- Advantages of microservices
- Bounded contexts and entities
- Reactive vs. declarative systems
- Using event storming to develop a DDD architecture
Skill Level Intermediate
- [Allen] Domain-driven design, or DDD, is an essential architectural process in both the microservice and the agile worlds. It's a great way to come up with an architecture for highly modular systems that can grow incrementally as the system evolves. In this course, we'll define DDD and walk through event storming, which is one of the most effective ways to develop a domain-driven design. We'll cover key concepts like Bounded Contexts, entities, and aggregates. We'll see how event-based systems work, and most importantly, I'll demonstrate the event storming process to you so you can see how a design actually comes together. Hi, I'm Allen Holub. I'm both a software architect, and an agile transformation consultant, and believe it or not, those two areas fit together like coffee and chocolate. You can't be agile if your system architecture can't stand up to the stress of constant change. DDD, the topic of this course, is a great solution to that problem. So please join me in my LinkedIn Learning course about domain-driven design and event storming.