Oliver Gierke demoes using Spring Data JPA to create repositories using a Domain-driven Design approach.
Richard Pawson discusses a case study of a large pure OO project for the Irish government, presenting the challenges met, the reason for choosing pure OO, and lessons learned implementing it.
Ian Bond presents the development of a trade flow event-driven architecture, providing the background of futures trade, the domain and the solution, sharing some of the lessons learned along the way.
Vaughn Vernon advocates using DDD’s strategic modeling patterns when integrating services in a RESTful SOA implementation, avoiding one of SOA’s pitfalls: focusing on services rather than the domain.
Eric Evans advocates on gradual blending of modeling and design into iterative development in an attempt to create a solution that expresses the domain and is flexible enough to support changes.
Johnsson refreshes the listeners’ memory on using value objects showing by example how their good use can revolutionize a program’s architecture, simplifying it, making it more readable and testable.
Jimmy Nilsson explains why DDD is different: it builds on collaboration and feedback, incorporates deep domain knowledge, having as end result: reduced complexity, testability, and maintainability.
Eric discusses the need for strategic thinking and how early design decisions can affect project and organization trajectories and why they involve much more than mere architecture.
Eric Evans reviews what he has learned in the 5 years since the publication of Domain Driven Design. 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.
Tim McCarthy talks about preserving the purity of the domain model while using frameworks. The presentation is targeted at developers and demoes a .NET SharePoint real application.