Domain-Driven Design is a team sport. Here’s my story of what can and cannot be accomplished with a team size of one. by Edward Barnard

The July 2022 article “Structure by Use Case” introduced the Bounded Context pattern, which we’ll be using over and over as we structure our software by use case. This month we’ll continue exploring these concepts as we implement the global Domain Event store. by Edward Barnard

We begin our implementation of Domain-Driven Design with simple refactoring. We’ll take a close look at what complexity might be hidden within the expected implementation. That observation will guide us in refactoring toward Domain-Driven Design. by Edward Barnard

Modern PHP software is well capable of large projects. We, therefore, need to approach architecture and design thoughtfully. That observation, unfortunately, runs at odds with our current “agile” methodologies. Here, we take a look at what went wrong and how it got that way. We’ll see the solution is “obvious.”

In this article, we’re going to look at using event and command buses to fulfil the use Cases of Uncle Bob’s Clean Code Architecture. By using commands and events, we will help our code have meaningful names for domain-driven design, as well as clear points to abstract our system logic.