this post was submitted on 01 Sep 2024
11 points (100.0% liked)

Domain-Driven Design

248 readers
1 users here now

"Domain-Driven Design is an approach to software development that centers the development on programming a domain model that has a rich understanding of the processes and rules of a domain. The name comes from a 2003 book by Eric Evans that describes the approach through a catalog of patterns. Since then a community of practitioners have further developed the ideas, spawning various other books and training courses. The approach is particularly suited to complex domains, where a lot of often-messy logic needs to be organized." -- Martin Fowler (link)

Rules

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

founded 1 year ago
MODERATORS
snowe@programming.dev
canpolat@programming.dev
11
The failed promise of Domain-Driven Design - part 1 (no-kill-switch.ghost.io)
submitted 2 months ago by lysdexic@programming.dev to c/ddd@programming.dev
1 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] marcos@lemmy.world 3 points 2 months ago

No, DDD isn't very helpful. It has only high-level concepts and it's hard to specialize into one's work.

But then, DDD is the most helpful technique we have. It's the one used every single time a project is successful, and for good reasons.