Concerns of Domain Driven Design

Let's talk about what problems domain driven design solves.

Domain driven design is a methodology to model several schemetic elements of an application. Domain driven design allows us to take a business domain, deconstruct schematic constructs and model our business domain with programming constructs we regularly use.

In fact, many of the principles of domain driven design are highly compatible with architectural models we use like reactive systems. You may even see some shared nomenclature.

And, similiarly to the reactive system methodology, its concerns include both technological demands and business demands. One of the primary motivations of domain driven design is its ability to create communication channels between developers and domain experts.

On the technological side, domain driven design allows us to take a large domain and model it into smaller subsections and how they interact. This can help us, for example, define the boundaries and responsibilities of our microservices or actors.

In conclusion, domain driven design is methodology to take business requirements in domain-specific language and convert it into a software model. It addresses business concerns and development concerns.