III. Architecture
This page will cover an overview of the architecture of the project. The architecture is based on the microservice architecture pattern.
For an easy overview of the project architecture, the C4 model is used. The C4 model is a hierarchical way to describe the architecture of a software system. It is based on a set of diagrams, each one describing a different level of abstraction. The C4 model is composed of four levels: System Context, Container, Component and Code. More about the C4 model
The following C4 model diagrams were created from the functional requirements of the project. That are described in the Features and Functionality section of the documentation.
As already described in the Features and Functionality section, the external systems payment and logistics where simplified.
The internal architecture of all four services is following the same patter, the Clean Architecture pattern, also known as Hexagonal or Onion Architecture. This pattern is based on the separation of concerns principle, which means that the code is separated into layers, each one with a specific responsibility.
More about the pattern and .net implementation
For example on the following image, we can see the layers and the core components of the Account Service:
On the above image each box or layer has its own project. All projects of a service are grouped in a Solution. With this approach we can identify the responsibilities of each layer and also its made sure that the dependency inversion principle must be followed. In .net we can only reference projects uni-directionally, so we can't have a domain class use a application class or infrastructure class by mistake.