There are a lot of options out there on how you should structure your DDD projects. Although DDD gives you a clear explanation of the different building blocks, it doesn’t prescribe any particular project setup or structure.
So this leaves it up to you (and everyone else) to create a structure that works for you. A possible setup I used before can be found below:
It is inspired on the blog articles below:
Applied Domain-Driven Design (DDD), Part 1 - Basics
Applied Domain-Driven Design (DDD), Part 2 - Domain events
Applied Domain-Driven Design (DDD), Part 3 - Specification Pattern
Applied Domain-Driven Design (DDD), Part 4 - Infrastructure
Applied Domain-Driven Design (DDD), Part 5 - Domain Service
Applied Domain-Driven Design (DDD), Part 6 - Application Services
Applied Domain-Driven Design (DDD), Part 7 - Read Model Services
Applied Domain-Driven Design (DDD), My Top 5 Best Practices
Applied Domain-Driven Design (DDD), Event Logging & Sourcing For Auditing
More information: https://github.com/zkavtaskin/Domain-Driven-Design-Example