This project is a simple application to create a Todo List Application, demonstrating a layered application architecture with DDD best practices. Implements for some NLayer Hexagonal architecture (Application, Infrastructure and Presentation Layers) and Domain Driven Design (Entities, Repositories, Domain/Application Services and so on) and aimed to be a Clean Architecture, with applying SOLID principles.
It should be noted that what I am implementing here is only a demonstration that does not reach all business logic, I only provide a few simple implementations and I am very happy if later when joining I can provide my experience that i have for actual cases.
Repository include layers divided by 4 project;
- Domain
- It’s responsible for implementing the application’s business logic and contains the entities and use cases. The Domain Layer is independent of the presentation and infrastructure layers and should only contain business logic that’s specific to the application.
- Application
- The Application Layer is responsible for implementing the application’s use cases. It acts as an intermediary between the presentation and domain layers and is responsible for executing the use cases by calling the appropriate domain layer methods.
- Infrastructure
- The Infrastructure Layer is responsible for implementing the application’s infrastructure, such as databases, external APIs, and file systems. It’s the layer that interacts with external systems and provides a way for the application to persist data.
- Presentation Layer
- The Presentation Layer is responsible for handling the user interface and presentation logic. It’s the layer that interacts with the user and provides a way for them to interact with the application.
- NET Core 6.0 (BackEnd)
- Angular (FrontEnd)
- Entity Framework Core (ORM)
- Message Brocker (RabbitMQ)
- NUnit
- etc
- Clean Architecture
- CQRS
- SOLID and Clean Code
- Domain Driven Design (Layers and Domain Model Pattern)