Dan North gives an overview of Domain Driven Design and Behavior Driven Development then ties them together for a powerful mix.
http://www.infoq.com/presentations/bdd-and-ddd

Dan Bergh 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, in a word, better.
http://www.infoq.com/presentations/Value-Objects-Dan-Bergh-Johnsson

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.
http://www.infoq.com/presentations/design-strategic-eric-evans

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.
http://www.infoq.com/presentations/ddd-eric-evans

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 involvement, and how we maintained a deep, malleable domain model, whilst meeting deadlines are also discussed.
http://www.infoq.com/presentations/rebuild-guardian-ddd-wills

This seminar talk will traverse the territory of architectural style within enterprise applications. Beginning with a brief survey of the prior art, it will propose candidate names and typical characteristics of architectural styles observed in the wild. Approaches to classifying architectural styles will be addressed, and potential benefits of classification reviewed. Finally the talk will treat the combination of different architectural styles, focusing on the use of SOA and DDD together as an example.

As software development leaders, we need to think more strategically. Some design decisions affect the trajectory of the whole project or even the organization. These decisions arise in early chartering and throughout development, and they are about much more than architecture. This talk will examine these issues through the lens of the Strategic Design principles of domain-driven design, which systematize a few critical practices some successful teams do intuitively. It is common for skilled teams to deliver software they are not proud of, due to compromises with legacy designs. Others …

StatoilHydro (former Statoil) has been using Domain-Driven Design in development of its oil trading and supply chain applications since 2004. Our hypothesis was that use of object oriented techniqes and thinking, strengthen through Domain Driven Design, combined with a proper object-relational mapping tool would significantly improve application performance and reduce the required code base compared with the current legacy systems. We will in this talk present our experiences with respect to required developer skills and technology.

Of all our design tools, creation of value objects is probable the most underused. This is the case especially considering its enormous potential to relieve entities and services from a lot of disturbing complexity. In this presentation we see some power-usage of the concept and how it can revolutionise your architecture, turning them inside out and conquering back much of our lost object orientation.

The tenets of Domain-Driven Design are well documented, and its mindshare has expanded massively in recent years, due to the brilliant work of Eric Evans and subsequent authors notably Jimmy Nilsson. However, knowledge on persisting domain models, especially in a performant and scalable way, is much less readily accessible. Lessons learned by architects of high-scale DDD-based systems in production settings are largely absent from the professional literature. And yet such knowledge should be of significant value to current practitioners responsible for the development or operation of DDD-based systems …