Application Design: Data-driven vs Domain-driven

blog.passwork.pro

Application Design: Data-driven vs Domain-driven

blog.passwork.pro

lysdexic@programming.dev to

Domain-Driven Design@programming.devEnglish · 2 years ago

The best way to handle modern programming paradigms.

You must log in or register to comment.

Chat

Domain-Driven Design@programming.dev

ddd@programming.dev

Create a post

You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !ddd@programming.dev

“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

Follow programming.dev rules
Be excellent to each other, no hostility towards users for any reason
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.

Visibility: Public

This community can be federated to other instances and be posted/commented in by their users.

1 user / day
1 user / week
1 user / month
1 user / 6 months
1 local subscriber
268 subscribers
17 Posts
2 Comments
Modlog