This is a practical guide for implementing Domain Driven Design (DDD). While the implementation details are based on the ABP Framework infrastructure, the basic concepts, principles and models can be applied to any solution, even if it is not a .NET solution.  

Architecture with .NET Core 3.1, ASP.NET Core 3.1, Entity Framework Core 3.1, C#, Angular 9.1, Clean Code, SOLID, DDD, Code Analysis, Docker and more. 

Technologies 

• .NET Core 3.1
• ASP.NET Core 3.1
• Entity Framework Core 3.1
• C# 8.0
• Angular 9.1
• Typescript
• JWT
• FluentValidation
• Scrutor
• Serilog
• Docker
• Azure DevOps
• ...

Practices 

• Clean Code
• SOLID Principles
• DDD (Domain-Driven Design)
• Unit of Work Pattern
• Repository Pattern 
• ...

Entity Framework half-heartedly supported Domain-Driven Design patterns. But the new-from-scratch EF Core has brought new hope for developers to map your well-designed domain classes to a database, reducing the cases where a separate data model is needed. EF Core 2.1 is very DDD friendly, even supporting things like fully encapsulated collections, backing fields and the return of support for value objects. In this session, we'll review some well-designed aggregates and explore how far EF Core 2.1 goes to act as the mapper between your domain classes and your data store. 

A curated list of Domain-Driven Design (DDD), Command Query Responsibility Segregation (CQRS), Event Sourcing, and Event Storming resources.

8 article(s) about "Domain-Driven Design" 

So, are CQRS commands part of the domain model? They are.