This talk was recorded at NDC Copenhagen in Copenhagen, Denmark. #ndccopenhagen #ndcconferences #developer #softwaredeveloper    

Attend the next NDC conference near you: 
https://ndcconferences.com
https://ndccopenhagen.com/

Subscribe to our YouTube channel and learn every day:   
/        @NDC 

Follow our Social Media!

https://www.facebook.com/ndcconferences
https://twitter.com/NDC_Conferences
https://www.instagram.com/ndc_conferences/

#dotnet #csharp 

Domain-Driven Design is one of the well-accepted approaches to build a large system with a maintainable codebase. It offers strategic and tactical patterns for software development. This talk focuses on the tactical patterns with a pragmatic approach and explains how to layer your software, how to practically implement aggregates, repositories, domain services, application services and other fundamental building blocks with real-world examples and well-defined rules.
The solution structure and code samples are based on .NET and C#.

NDC Conferences

Domain-Driven Design (DDD) helps build maintainable codebases by separating business logic into domain and application layers. Key patterns include aggregates (clusters of tightly-coupled objects saved as units), repositories (only for aggregate roots, no business logic), specifications (reusable filters), and domain services (for cross-entity business rules). Entities enforce validity through constructors and methods with private setters. Application services orchestrate use cases using DTOs, never exposing entities. Input DTOs should be use-case-specific; output DTOs can be reused. Never map input DTOs directly to entities—use constructors and domain methods. Domain logic is core and reusable; application logic is use-case-specific (authorization, payments, emails). This layered approach keeps code simple, consistent, and testable across multiple application types.

Implementing Domain Driven Design as a Pragmatic .NET Developer - Halil İbrahim Kalkan