Three different system architectures

1. Monolithic System with one data source

In a monolithic architecture, a single application exists on the server side, containing the application's entire API.

An advantage of this architectural approach is the application's low complexity.

Disadvantages include inefficient scalability and the fact that the entire application must be shut down to install a new version. Under high server load, an additional monolith must be started to handle requests from the many clients.

A monolith is generally the first choice when launching new software. This approach is preferable when the expected server load is not yet clear, as it avoids unnecessary complexity.

2. Distributed System with one shared data source

In a distributed architecture with a shared database, multiple applications exist on the server side that collectively constitute the application's entire API.

An advantage of this architectural variant is the improved scalability of the server application. For instance, in the case of an online store, there might be three separate applications handling products, customers, and orders. Product data is typically maintained by only a few employees; consequently, the product API sees significantly less traffic than, say, the order API in a busy store. During peak times, only additional instances of the order module need to be launched, while the product module continues to run with just a single instance. Another advantage is that the entire application landscape does not need to be shut down. If the product module requires an update, for example, customers can still place ordersâ€”a clear benefit for the store's revenue.

A disadvantage of this architecture is the increased complexity on the server side. Furthermore, despite distributing the API across multiple modules, the shared database can become a bottleneck, as it receives requests from all the server modules' APIs. However, the data remains synchronized thanks to the database's consistency mechanisms.

This architecture makes sense when the load varies significantly across the different module APIs. This can justify the effort of managing multiple applications, as opposed to using a monolithic architecture.

3. Distributed System with synchronized data sources

The distributed architecture with multiple databases, also known as classic microservice architecture, has the highest complexity.

The advantage of this architecture variant is the high scalability of the server landscape. The additional distribution of the database model can eliminate the potential bottleneck of the shared database architecture.

The disadvantage of this architecture is the introduction of asynchrony between the databases. The data is only eventually consistent at any given time. The consistency between the databases is only established with a time delay via a so-called message broker. This can result in clients receiving conflicting information. For example, there could be 15 reviews for a product on a shop website, even though the headline says 14 reviews, because the 15th review was just written by me. This asynchrony can be unpleasant, but tolerable. However, it can also be unacceptable when it comes to sensor data in a technical device, for example, where the sensor value accurate to the second is required for real-time control. In this case, synchrony must be enforced. This then comes at the expense of the availability of the server landscape.

The microservice architecture should only be used if the framework conditions make it absolutely necessary due to an extremely large number of API clients.

3.1 Module Coupling

(1)	(2)	(3)	(4)	(5)	(6)	(7)	(8)	(9)	(10)	(11)	Module
5.00	2.00	1.00	0.00	0.00	0.00	1.00	2.00	0.00	1.00	1.00	(1) EventService
2.00	5.00	1.00	1.00	0.00	1.00	1.00	0.00	1.00	2.00	0.00	(2) VenueAreaService
2.00	1.00	4.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	(3) EventSeriesService
0.00	1.00	0.00	4.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	(4) GastronomyUnitService
0.00	0.00	0.00	0.00	4.00	0.00	0.00	0.00	0.00	0.00	0.00	(5) JobLocationService
0.00	1.00	0.00	0.00	0.00	3.00	0.00	0.00	1.00	1.00	0.00	(6) BookingService
1.00	1.00	0.00	0.00	0.00	0.00	3.00	0.00	0.00	0.00	0.00	(7) OrganizerService
1.00	0.00	0.00	0.00	0.00	0.00	0.00	3.00	0.00	0.00	0.00	(8) SportsTeamService
0.00	1.00	0.00	0.00	0.00	1.00	0.00	0.00	3.00	0.00	0.00	(9) CustomerService
1.00	2.00	0.00	0.00	0.00	1.00	0.00	0.00	0.00	3.00	0.00	(10) SeatService
1.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	3.00	(11) PageService

3.2 Normalized Module Coupling

(1)	(2)	(3)	(4)	(5)	(6)	(7)	(8)	(9)	(10)	(11)	Module
0.38	0.15	0.08	0.00	0.00	0.00	0.08	0.15	0.00	0.08	0.08	(1) EventService
0.14	0.36	0.07	0.07	0.00	0.07	0.07	0.00	0.07	0.14	0.00	(2) VenueAreaService
0.29	0.14	0.57	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	(3) EventSeriesService
0.00	0.20	0.00	0.80	0.00	0.00	0.00	0.00	0.00	0.00	0.00	(4) GastronomyUnitService
0.00	0.00	0.00	0.00	1.00	0.00	0.00	0.00	0.00	0.00	0.00	(5) JobLocationService
0.00	0.17	0.00	0.00	0.00	0.50	0.00	0.00	0.17	0.17	0.00	(6) BookingService
0.20	0.20	0.00	0.00	0.00	0.00	0.60	0.00	0.00	0.00	0.00	(7) OrganizerService
0.25	0.00	0.00	0.00	0.00	0.00	0.00	0.75	0.00	0.00	0.00	(8) SportsTeamService
0.00	0.20	0.00	0.00	0.00	0.20	0.00	0.00	0.60	0.00	0.00	(9) CustomerService
0.14	0.29	0.00	0.00	0.00	0.14	0.00	0.00	0.00	0.43	0.00	(10) SeatService
0.25	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.00	0.75	(11) PageService

3.3 Coupling Analysis

Modules	11
Global Entities	40
Min. Entities per Module	3
Max. Entities per Module	5
Average Entities per Module	3.64
Local-only Entities	19
Distributed Entities	21
Transfer Entities	34
Inter-Process-Transfers	28
Max-Possible-Process-Transfers	110
Transfer Effort	25.5
Isolation Quality	15.0