Event choreography vs orchestration in Kafka - Quick Revision & Key Differences

Recall & Review

beginner

What is event choreography in event-driven systems?

Event choreography is a decentralized approach where each service listens for events and reacts independently without a central controller. Services communicate by producing and consuming events directly.

beginner

What is event orchestration in event-driven systems?

Event orchestration uses a central controller (or orchestrator) that directs the flow of events and tells services what to do and when, coordinating the overall process.

intermediate

How does Kafka support event choreography?

Kafka acts as a message broker where services publish and subscribe to event topics. Each service independently reacts to events it cares about, enabling choreography without a central controller.

intermediate

What is a key advantage of event choreography over orchestration?

Choreography reduces tight coupling by letting services act independently, which can improve scalability and flexibility since no central controller is needed.

intermediate

When might event orchestration be preferred over choreography?

Orchestration is preferred when you need clear control over the sequence of events, easier error handling, and centralized monitoring of the workflow.

In event choreography, who controls the flow of events?

A Each service controls itself independently

B A central orchestrator controls all events

C The database controls the events

D The user manually triggers events

In choreography, each service listens and reacts independently without a central controller.

Which Kafka feature is essential for event choreography?

A Topics for publishing and subscribing events

B Centralized workflow engine

C Direct service-to-service calls

D Database triggers

Kafka topics allow services to publish and consume events independently, enabling choreography.

What is a main benefit of event orchestration?

A Decentralized control

B Centralized control and monitoring

C No need for event brokers

D Services never communicate

Orchestration uses a central controller to manage event flow and monitor the process.

Which approach can improve scalability by reducing tight coupling?

A Synchronous API calls

B Event orchestration

C Event choreography

D Monolithic design

Choreography lets services act independently, reducing tight coupling and improving scalability.

When is event orchestration more suitable than choreography?

A When you want no central monitoring

B When you want decentralized control

C When services never communicate

D When you need strict sequence and error handling

Orchestration is better for strict control of event sequences and easier error handling.

Explain the difference between event choreography and event orchestration in simple terms.

Think about who tells the services what to do.

Describe a scenario where event choreography would be better than orchestration and why.

Imagine many services working independently without waiting for a boss.