Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update event-driven-architecture.md #3318

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update event-driven-architecture.md #3318

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions content/en/event-driven-architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,3 +22,7 @@ Event-driven architectures establish a central hub for all events (e.g., Kafka).
You then define the event producers (source) and consumers (receiver), and the central event hub guarantees the flow of events.
This architecture ensures that services remain decoupled and events are properly routed from the producer to the consumer.
The producer will take the incoming event, usually by HTTP protocol, then route the event information.

## Challenges

Error handling and data loss are two main challenges of using event-driven architecture.