|
You are here |
olano.dev | ||
| | | | |
vladikk.com
|
|
| | | | | Let's do a little experiment: try to explain the gist of Domain-Driven Design to someone who has no clue about it. This, especially doing it succinctly, is not easy. Heck, I struggle with it myself. Bounded contexts, entities, domain events, value objects, domains, aggregates, repositories... where do you even start? To find the order in the apparent chaos, I want to analyze the DDD methodology from a rather unusual perspective - by applying Domain-Driven Design to Domain-Driven Design itself. After all, this methodology is intended to deal with complex domains, isn't it? | |
| | | | |
nickhayden.com
|
|
| | | | | I started a new role in October that has a strong focus on event sourcing and domain driven design (DDD). One of the recommended books in our on-boarding materials is Domain-Driven Design Distilled... | |
| | | | |
rachelcarmena.github.io
|
|
| | | | | Trying to explain DDD easily | |
| | | | |
williamdurand.fr
|
|
| | | Domain Driven Design also known as DDD is an approach to develop software for complex needs by connecting the implementation to an evolving model. It is a way of thinking and a set of priorities, aimed at accelerating software projects that have to deal with complicated domains. | ||