maece/HSG-MCS-HS21_tapas
1
0
Fork 0
Code Issues 14 Pull Requests Packages Projects Releases 6 Wiki Activity

Update 0001-microservice-architecture.md

Browse Source
This commit is contained in:
Julius Lautz 2021-12-23 11:37:57 +01:00 committed by GitHub
parent 70cf269dde
commit fff7c5e816
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
TAPAS-Final/doc/architecture/decisions/0001-microservice-architecture.md
View File

@ -14,7 +14,7 @@ The system is made up of five distinct bounded contexts, namely the Task Domain,
The system will follow the Microservice architecture. The system will follow the Microservice architecture.
The Microservices architecture suits our system's driving architectural characteristics particularly well. Scalability and fault tolerance are two of the systems top 3 driving characteristics and elasticity and evolvability are two of the systems other driving characteristics. These are all characteristics that the Microservices architecture excels at. Furthermore, none of our system's driving characteristics is hindered by the Microservices architecture (none of them have below 3 stars our of 5). The Microservices architecture suits our system's driving architectural characteristics particularly well. Scalability and fault tolerance are two of the systems top 3 driving characteristics and elasticity and evolvability are two of the systems other driving characteristics. These are all characteristics that the Microservices architecture excels at. Furthermore, none of our system's driving characteristics is hindered by the Microservices architecture (none of them have below 3 stars out of 5).
We do not expect to have a single monolithic database, so this is not a concern. We do not expect to have a single monolithic database, so this is not a concern.