It doesn’t matter how many entities, aggregates, factories, services, and repositories you have. That’s not domain-driven design. There

Stop Pretending To Do Domain-Driven Design

submited by

Style Pass

2024-10-27 11:00:04

It doesn’t matter how many entities, aggregates, factories, services, and repositories you have. That’s not domain-driven design.

There’s a trend by software developers to approach domain-driven design as a collection of useful programming/coding patterns and abstractions:

I see this idea popularized on all the social platforms by content creator X software developer with 3 years of experience who is an expert on building distributed microservices using domain-driven design. They can tell you all about creating entities, aggregates, and repositories. And distributed microservices too – as a cherry on the top.

The courses on popular learning platforms are the same. Here’s part of a description from a popular learning platform’s course on DDD:

Vaughn also writes about a fictitious scenario of developers focused on these tactical tools – calling it “DDD-Lite“: