The most complicated aspect of large software projects is not the implementation, it is the real world domain that the software serves. Domain Driven Design is a vision and approach for dealing with highly complex domains that is based on making the domain itself the main focus of the project, and maintaining a software model that reflects a deep understanding of the domain. The vision was brought to the world by Eric Evans in his book "Domain Driven Design". Eric's work was based on 20 years of widely accepted best practices in the object community, as well as Eric's own insights. Domain Driven Design Quickly is a short, quick-readable summary and introduction to the fundamentals of DDD. A special interview with Eric Evans on the state of Domain Driven Design is also included.
Showing posts with label Domain Driven Design. Show all posts
Showing posts with label Domain Driven Design. Show all posts
Thursday, July 7, 2011
InfoQ: Domain Driven Design Quickly
InfoQ: Domain Driven Design Quickly
Domain Driven Design: A Step by Step Guide - Part 1 - Java tutorial - developer Fusion
Domain Driven Design: A Step by Step Guide - Part 1 - Java tutorial - developer Fusion
There is a lot of interest in DDD recently, both in the book, and in the methodology, and in the buzzword. As a book and methodology, DDD is an excellent way to approach complex software problems, and make them far more understandable and manageable. As a buzzword, DDD is in danger of being corrupted like many other good software practices.
To try and clear up some of the confusion around DDD, I am intending to start a series of articles, covering aspects of DDD and trying to demystify it.
Subscribe to:
Posts (Atom)