This solutions implements a minimal Tax schedules via web api.
With docker installed, run to build:
$ docker-compose up
It aims to simulate some daily activities of a sofware development in the company.
We are using Swagger for easier documentation and to allow us to call the api easier.
Access the webpage from any browser:
https://localhost:5000/swagger/
All documentation necessary for the endpoints should be in the swagger page.
The architecture is simple, the client sends a message to controllers and the controllers uses a Postgre database to persist data.
This will contain all entities, enums, exceptions, interfaces, types and logic specific to the domain layer.
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.
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.
This layer is a webapi that allow clients to call rest endpoints. 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.
- I would introduce a better logger platform for the project like logstash or kibana.
- I would never use passwords in the code as I have done here. Instead, I would setup using builds like github actions, azureDevops actions and pass it as environment variables.
- If I more times, I would do some improvements on my integration tests.
MIT