Jimmy Nilsson makes a case for DDD explaining that while DDD uses some similar elements as DB-driven design does, for example, entities and repositories, the difference is in how they are used, the way the design is approached and elaborated, building on collaboration and feedback, incorporating deep domain knowledge, having as end result: reduced complexity, testability, and maintainability.
Eric discusses the need for strategic thinking an how early design decisions have major impact on the organization and the entire development process. He uses the lens of DDD Strategic Design principles (emphasizing "Context Mapping" and "Distilling the Core Domain") to show how to avoid strategic failures and achieve strategic successes. Winning strategy starts with the domain.
Eric Evans reviews what he has learned in the 5 years since the publication of Domain Driven Design - what works, what doesn't work, and how to conceptualize and describe it all. He argues that the fundamentals have held up well but there are differences in how I do things and look at things now. He also describes some new patterns and talks about changes of emphasis for existing patterns.
This presentation explores how the platform driving the guardian.co.uk, (3 time winner of the 'Best Newspaper' Webby), site was almost completely rebuilt using the principles of DDD. Key evolutions of our model, how DDD encouraged domain experts to greater iinvolvement, and how we maintained a deep, malleable domain model, whilst meeting deadlines are also discussed.
In this presentation recorded during QCon SF 2008, Tim McCarthy talks about preserving the purity of the domain model while using frameworks. Frameworks can be very useful when developing applications, but they can present some pitfalls, mudding the domain, if they are not used properly. The presentation is targeted at developers.