-
Notifications
You must be signed in to change notification settings - Fork 0
Web Backend
Our backend project was created in Clean Architecture/N-Layers structure.
Binder.Core, Binder.Application, Binder.Infrastructure are directly Clean layers, represented as DLLs files after build, Binder.API is Clean's Presentation layer, represented as executable file.
Additionally, there is abstract folder called Tests with Binder.UnitTests and Binder.IntegrationTests projects for automated tests.
For current dependencies list, please check out solution's NuGet listing.
App is presenting REST API endpoints set.
How is data flow organised:

How DTOs data mapping is organised:

For this project, follow all guidelines from Clean Architecture pattern.
Limit all domain's data (constants and domain info representations) to Binder.Core layer.
If there's some user's data (needed during debelopment) use configuration files for them.
If you need to use some sensitive data, use GitHub Secrets service, do NOT add them to repo or code.
Please let us know about it via bug report on Binder's project repo.