Mirrors/api-guidelines
1
0
Fork 0
mirror of https://github.com/adidas/api-guidelines.git synced 2025-10-25 15:19:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fixing figure description for new images

Browse Source
This commit is contained in:
Juan Manuel Pérez
2024-04-25 12:54:50 +02:00
parent 1ea1f3c90e
commit 1264f4109e
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
asynchronous-api-guidelines/01_introduction/b_basic_concepts.md
View File

@@ -30,11 +30,11 @@ In most cases, EDAs are broker-centric, as seen in the diagram below.
Typically, the architectural landscape of a big company grows in complexity and as a result of that it is possible to end up with a bunch of direct connections between a myriad of different components or modules.
![EDA overview](../../assets/eda_problem_statement_1.png)
![Typical architecture diagram](../../assets/eda_problem_statement_1.png)
By using streaming patterns, it is possible to get a much cleaner architecture
![EDA overview](../../assets/eda_problem_statement_2.png)
![EDA architecture diagram](../../assets/eda_problem_statement_2.png)
It is important to take into account that EDAs are not a silver bullet, and there are situations in which this kind of architectures might not fit very well.