From d3daa9433c9133702dfdcf6bf076639f412822fc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Juan=20Manuel=20P=C3=A9rez?= Date: Thu, 25 Apr 2024 13:22:56 +0200 Subject: [PATCH] Additional fixes (III) --- asynchronous-api-guidelines/01_introduction/b_basic_concepts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/asynchronous-api-guidelines/01_introduction/b_basic_concepts.md b/asynchronous-api-guidelines/01_introduction/b_basic_concepts.md index ad4d5ab..18b6af0 100644 --- a/asynchronous-api-guidelines/01_introduction/b_basic_concepts.md +++ b/asynchronous-api-guidelines/01_introduction/b_basic_concepts.md @@ -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. - 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.