Architecting and Implementing Domain-Driven Design Patterns with Microsoft .NET

Play Architecting and Implementing Domain-Driven Design Patterns with Microsoft .NET
Sign in to queue


Domain-Driven Design (DDD) is an approach to software design and development that focuses on the analysis of the business domain and uses ad hoc tools such as the ubiquitous language to split the business domain into distinct subdomains, each of which becomes a bounded context and requires its own architectural approach. After a brief introduction on the foundation of the DDD approach (mostly ubiquitous language and bounded contexts), we focus on a reference .NET application and discuss its implementation of the Domain Model pattern (aggregates, POCO domain entities, value objects, domain services) while contrasting the use of anemic domain models. Next, we compare the Domain Model implementation to the CQRS pattern. In a CQRS architecture, the business logic of the application is expressed in terms of command and events and queries take place on a physically segregated stack. Along the way, we emphasize the role and structure of the persistence layer and touch on cross-cutting concerns (scalability, caching, security) and dependency injection to protect domain logic from infrastructure technologies. Overall, this session presents the state-of-the-art for enterprise application architecture and development in .NET. By attending this session, you’ll get a global vision of the fundamental DDD patterns and see them implemented in reference application.



Session Type:





Hall 8.1 Room G



Right click to download this episode

The Discussion

  • User profile image

    Good introduction to the first part. The part i liked the most are the factories inside the class and make the constructors private. Although for factories I trend to put them in another file inside the domain...

Add Your 2 Cents