Domain Driven Design

Fundamentally, DDD is the principle that we should be focusing on the deep issues of the domain our users are engaged in, that the best part of our minds should be devoted to understanding that domain, and collaborating with experts in that domain to wrestle it into a conceptual form that we can use to build powerful, flexible software.

This is a principle that will not go out of style. It applies whenever we are operating in a complex, intricate domain. Agile processes have had enough influence that most projects now have at least an intention of iterating, working closely with business partners, applying continuous integration, and working in a high-communication environment. So DDD looks to be increasingly important for the foreseeable future, and some foundations seem to be laid. This track will take you through these foundations, and how they are applicable and actually applied in projects.