Uncle bob said : “The Goal of software architect is to minimize the human resources required to build and maintain the required system”.(Robert C.Martin) I often use terms that people associate with…

Roberto Umbelino

Figma

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Domain Driven Design is a recommended approach for developing large systems with complex business logic. It focuses on defining boundaries and modeling the actual domain rather than relying solely on patterns. Transaction Script and Table Module are examples of domain logic patterns that can be used in smaller applications with less complexity.

DDD or not DDD ?

Do you believe that Domain-Driven Design is essential for all types of projects or only for more complex systems?

Just do CRUD with a proper PATCH implementation and data model.
Most of the time, people who are supposed to understand the domain, don’t. Trying to do DDD in such situations is not very smart. You need to get things done and ship value. The customer doesn’t care if you are not done yet describing and designing the domain.

Imagine a guy with slavic accent saying “idth’ deepänds”
and guess what? He’s propably right!