https://github.com/nikiforovall/na-es
Event Sourcing, Clean Architecture, and DDD template
https://github.com/nikiforovall/na-es
clean-architecture dotnet6 eventsourcing
Last synced: 20 days ago
JSON representation
Event Sourcing, Clean Architecture, and DDD template
- Host: GitHub
- URL: https://github.com/nikiforovall/na-es
- Owner: NikiforovAll
- License: apache-2.0
- Created: 2021-10-31T16:01:56.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2021-11-13T17:07:21.000Z (over 3 years ago)
- Last Synced: 2025-02-12T11:53:54.414Z (2 months ago)
- Topics: clean-architecture, dotnet6, eventsourcing
- Language: C#
- Homepage: https://github.com/NikiforovAll/na-templates
- Size: 254 KB
- Stars: 1
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# NikiforovAll.EventSourcing.Template \[na-es\]
## Technologies
* [ASP.NET Core 6](https://docs.microsoft.com/en-us/aspnet/core/)
* [FluentValidation](https://fluentvalidation.net/)
* [MediatR](https://github.com/jbogard/MediatR)
* [AutoMapper](https://automapper.org/)
* [MartenDB](https://martendb.io/)
* [MassTransit](https://masstransit-project.com/)
* [Docker](https://www.docker.com/)
Testing:
* [XUnit](https://xunit.net/)
* [FluentAssertions](https://fluentassertions.com/)
* [Moq](https://github.com/moq)
* [AutoFixture](https://github.com/AutoFixture/AutoFixture)
* [Respawn](https://github.com/jbogard/Respawn)
## Principles
* Event Sourcing
* CQRS
* DDD
* Testability
* Separation of Concerns
## Overview
Reference to
### Domain
This will contain all entities, enums, exceptions, interfaces, types and logic specific to the domain layer.
### Application
This layer contains all application logic. It is dependent on the domain layer, but has no dependencies on any other layer or project. This layer defines interfaces that are implemented by outside layers. For example, if the application need to access a notification service, a new interface would be added to application and an implementation would be created within infrastructure.
### Infrastructure
This layer contains classes for accessing external resources such as file systems, web services, smtp, and so on. These classes should be based on interfaces defined within the application layer.
### Api
This layer depends on both the Application and Infrastructure layers, however, the dependency on Infrastructure is only to support dependency injection. Therefore only *Startup.cs* should reference Infrastructure.
## License
This project is licensed with the [Apache License](LICENSE).
## Credit
Inspired by:
*
*
*
*
*