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

Additional fixes (III)

Browse Source
This commit is contained in:
Juan Manuel Pérez
2024-04-25 13:22:56 +02:00
parent 51537a979f
commit d3daa9433c
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -46,7 +46,7 @@ Also, it is important to note that it is possible to mix request-driven and even
- Online services that interact directly with a user fits better into the synchronous communication but they also can generate events into Kafka. - Online services that interact directly with a user fits better into the synchronous communication but they also can generate events into Kafka.
- On the other hand, offline services (billing, fulfillment, etc) are typically built purely with events. - On the other hand, offline services (billing, fulfillment, etc) are typically built purely with events.
#### Kafka as the heard of EDAs #### Kafka as the heart of EDAs
There are several technologies to implement event-driven architectures, but this section is going to focus on the predominant technology on this subject : Apache Kafka. There are several technologies to implement event-driven architectures, but this section is going to focus on the predominant technology on this subject : Apache Kafka.