this post was submitted on 30 Oct 2025
2 points (100.0% liked)

Domain-Driven Design

295 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 2 years ago
MODERATORS
snowe@programming.dev
canpolat@programming.dev
2
Eliminate the Complexities of Event driven Architecture! (www.youtube.com)
submitted 5 days ago by codeinabox@programming.dev to c/ddd@programming.dev
0 comments fedilink hide all child comments
 

The distributed nature of modern applications and their architectures brings a great level of complexity to engineering teams. Though API contracts, asynchronous communication patterns, and event-driven architecture offer assistance, not all enterprise teams fully utilise them. While adopting cloud and modern technologies, teams are often hurried to produce outcomes without spending time in upfront thinking. This leads to building tangled applications and distributed monoliths. For those organisations, it is hard to recover from such costly mistakes.

In this talk, Sheen will explain how enterprises should decompose by starting at the organisational level, applying Domain-Driven Design, and distilling to a level where teams can operate within a boundary, ownership, and autonomy. He will provide organisational, team, and design patterns and practices to make the best use of event-driven architecture by understanding the types of events, event structure, and design choices to keep the domain model pure by guarding against corruption and complexity.

no comments (yet)
sorted by: hot top controversial new old
there doesn't seem to be anything here