<< Back to Values and PracticesEditIntroduction
Domain Driven Design (DDD) is a pattern language grown from experience over the past few decades.
Eric Evans wrote the book on the subject,
Domain-Driven Design: Tackling Complexity in the Heart of Software, coining the term "DDD" and distilling years of experience in applying technique and patterns centered on the
DomainModel style of organizing business logic. In many respects, it is more a mindset than a methodology or technology and is based on a few major points:
- For most software projects, the primary focus should be on the domain and domain logic and surfacing the UbiquitousLanguage.
- Complex domain designs should be based on a model and models should be considered within the BoundedContext of the domain.
- Software models can be captured effectively in object oriented code, reducing or eliminating the need for.
If you're just getting started with DDD or are an beginner-to-intermediate OO developer, we recommend you check out the free book from InfoQ,
Domain Driven Design Quickly.
EditResources
http://domaindrivendesign.org/
Fundamental DDD ~ A slideshow by Dave Laribee
Design-Driven Design forumEditScreencasts
Putting the Model to Work - Eric Evans
Improving Application Design with a Rich Domain ModelEditBooks
Domain Driven Design Quickly (Eric Evans, FREE Mini-book from InfoQ!)
Domain-Driven Design: Tackling Complexity in the Heart of Software (Eric Evans)
Applying Domain-Driven Design And Patterns (Jimmy Nilsson)
Patterns of Enterprise Application Architecture (Martin Fowler)
Currently rated 3.1 by 190 people
- Currently 3/5 Stars.
- 1
- 2
- 3
- 4
- 5