/explore
|
You are here 
|
williamdurand.fr | ||
| | | | |
www.paepper.com
Domain Driven Design (DDD) is an influential book by Eric Evans from 2004 - sometimes also referred to as "the big blue book". This blog post summarizes some of my own understanding of the book and gives you an introduction to domain driven design. Important definitions Domain The domain is the area in the real world which we are writing a computer program about. Model The model is our representation of our domain. Generally, the model represents a subset of our domain at an appropriate abstraction level to be able to solve problems related to that domain. |
|
| | | | | ||
| | | | |
blog.gougousis.net
[AI summary] A developer provides a critical re-reading of Domain-Driven Design, contrasting tactical patterns with the strategic importance of domain modeling, ubiquitous language, bounded contexts, domain events, and aggregates. |
|
| | | | | ||
| | | | |
www.softdevtube.com
The onion architecture is not as well known as the 3-tier software architecture but is gaining a lot of attention during the microservices era. It structures your software so that it is easy to change technologies without impacting business logic. Coupled with Domain Driven Design (DDD) principles it offers a powerful way to build a |
|
| | | | | ||
| | | | |
venam.net
We're used, as software engineers to try to make things perfect, to see things from above, to think we're great architects and creators. What's more important though is to create software that does an important job for someone. What are the best ways to create such software? |
|
| | | |||
