Domain-Driven Design for Monoliths

While domain-driven design (DDD) has proved itself as a powerful software design tool, it’s still underutilized. Many refrain from DDD thinking that it’s an all-or-nothing affair—either you implement every pattern the methodology has to offer, or you don’t do it all. Others miss strategic opportunities thinking that DDD can only be applied on greenfield projects. The truth is that not only can brownfield projects benefit from DDD, but often they desperately need it to solve the challenges in legacy systems.

For example, when documents are mostly outdated and business domain knowledge is spread across different stakeholders, cultivating a shared understanding of the business domain through event storming is an effective way to recover the knowledge. Building a context map makes it easy to spot sociotechnical design issues, while contexts integration patterns guide on how to improve these strategic decisions. Last but not least, with DDD’s subdomains, you can evaluate the project’s business logic implementation and spotlight the areas that need improvement or refactoring the most.

Join expert Vladik Khononov to learn how to apply DDD on brownfield projects—the type of projects we work on the most in real life. You’ll explore the strategic aspect of DDD and learn to selectively apply its patterns and practices to gain and recover domain knowledge, improve modularity, and, most importantly, continuously evolve design decisions aligning them with the software’s business strategy and goals.