"Architecture decisions usually involve the structure of the application or system, but they may involve technology decisions as well, particularly when those technology decisions impact architecture characteristics." (Fundamentals of Software Architecture by Mark Richards an Neal Ford)
In the following table you will find a list with all ADRs (Architecture Decision Records) made for Road Warrior.
| Decision | Summary |
|---|---|
| 0000-template | We need to record the architectural decisions made on this project. |
| 0001-UsersActivity | Requirement refers to the "active users" amount. We need to separate Active and other users naming. Also defining how to distinguish active users. |
| 0002-UI scopes | UI functionality needs to be limited and UI's need to be defined. |
| 0003-RDBMS_for_user_data | For the solution strategy of the Online Trip Management Dashboard, we are faced with a critical decision regarding the storage and management of user data |
| 0004-PWA | For the solution strategy of the Online Trip Management Dashboard, we are faced with a significant architectural decision regarding the choice of technology for creating the user interface and providing an enhanced user experience. |
| 0005-Containerization | For the solution strategy of the Online Trip Management Dashboard, we are faced with architectural decision concerning packaging and managing the application. |
| 0006-API-Integration | The choice of an API technology for our backend services. |
| 0007-Message-Broker | A message broker technology for enabling asynchronous communication. |
| 0008-API-Gateway | The API Gateway will serve as a central entry point for incoming requests to our microservices. |
| 0010-architectural-style-decision | In response to the requirements presented by a new startup aiming to create a next-generation online trip management dashboard, we are tasked with making architecture style decision to meet the demands of a large user base and complex functionality. |
| 0011-microservices_with_shared_database | We have identified the need to maintain data consistency and reduce data redundancy while still benefiting from the advantages of a microservices architecture. |