📄️ Introduction
The purpose of this section is to expose and explain the architectural choices related to the Profile API solution.
📄️ Clean Architecture
As the Profile API is quite large, its architecture is oriented in the direction that gives the best scalability and maintainability. After numerous researches on the subject, it has been decided to go with the “Clean Architecture” which is a variant of the “Hexagonal Architecture” and the “Onion Architecture”:
📄️ Database
This section gives information about the database of the Profile API.
📄️ Design patterns
As the “Clean Architecture” is only a concept, the best way to structure an API around design patterns that have proven themselves has been researched.
📄️ Solution
Structure
📄️ Technologies
List of the most important external libraries used by the Profile API.
📄️ Testing
Thanks to this architecture, this application has unit and/or integration tests for all its layers which helps a lot validating the