Eric Evans: Domain-Driven Design. Tackling complexity in the heart of software, Upper Saddle River, NJ: Addison-Wesley (2003; 2006 ed)
- Buy the book on Amazon (affiliate link)
- DDD opened my eyes for a totally different kind of structure in code, and software architecture in general. This could’ve actually been the first book of its kind that made me realize that Design Patterns aren’t all there is, and that there’s a higher-level order.
Full reference I use in my notes:
[#evans2006ddd]: Eric Evans (2006):
_Domain-Driven Design. Tackling complexity in the heart of software_,
Upper Saddle River, NJ: Addison-Wesley.
Related Writing
In the Wiki:
These posts are e.g. tagged with #ddd.
Find yourself dealing with primitive value types a lot? There’s a term for that.
Core Data is Invasive. You Can Hide It, Or You Can Embrace It
Modeling: From Structured Data Representation to Problem Domain
How to Create Flexible Components with Two Levels of Service Objects
Where Instead of Using Functional Bind, I Create an Expressive Model
I'm About to Release a Little E-book on Domain-Driven Design and Mac Application Development