Explore >> Select a destination
|
You are here 
|
softwarepatternsdemystified.wordpress.com | ||
| | | | |
enterprisecraftsmanship.com
|
|
| | | | | There's an interesting controversy between two DDD topics: the Specification pattern and the Always-Valid domain model. | |
| | | | |
herbertograca.com
|
|
| | | | | Domain-Driven Design was coined by Eric Evans in his fantastic bookDomain-Driven Design: Tackling Complexity in the Heart of Software, published in 2003. Eric Evans book was key in formalisingmany of the software development concepts that today we take for granted. | |
| | | | |
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. | |
| | | | |
nodogmablog.bryanhogan.net
|
|
| | | Full source code available here. Over the past couple of years I wrote a few posts about Dependency Injection in .Net Core 2.1, and this week I received comments from a reader telling me that some of the changes in . | ||
