by Jimmy Bogard
At its heart, much of Domain-Driven Design is all about object-oriented design. The challenge with elegant designs is that they all start out ugly. But our domain objects don't need to stay as anemic, data-centric property bags. With a small set of well-honed refactoring techniques, we can turn an ugly domain model into a wicked domain model, where our business objects respect boundaries, take our commands, and never, ever find themselves in a bad state.
by Greg Major
Domain Driven Design (DDD) holds the promise of enabling teams to deliver high-value line-of-business applications. While DDD is as much an overall approach rather than a specific architecture, this session will focus on implementing real world DDD applications from the ground up. Together we will explore domain isolation and discuss practical approaches to each layer using .NET. You will learn about common design patterns in DDD architectures such as the Repository, Unit of Work, and Data Transfer Object. We will also see first-hand how tools such as NHibernate, Unity, Automapper, WCF, and the Enterprise Library can help (or in some cases hinder) our ability to deliver maintainable solutions to our customers.
20th August 2011