Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Web Backend

Strayker edited this page Jan 9, 2024 · 6 revisions

File & Logic Structure

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:

data-flow-diag

How DTOs data mapping is organised:

dto-mapping-diag

Code & values locations

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.

Clone this wiki locally