Event-driven vs request-driven in Microservices - Quick Revision & Key Differences

Recall & Review

beginner

What is a request-driven architecture in microservices?

Request-driven architecture means services communicate by sending direct requests and waiting for responses, like making a phone call to ask for information.

beginner

Define event-driven architecture in simple terms.

Event-driven architecture means services react to events or messages sent by others without waiting, like receiving a notification and acting on it when it arrives.

intermediate

What is a key benefit of event-driven architecture over request-driven?

Event-driven architecture allows services to work independently and handle tasks asynchronously, improving scalability and fault tolerance.

intermediate

What is a common challenge when using request-driven communication?

Request-driven communication can cause tight coupling and delays because services wait for responses, which may slow down the system if one service is slow or down.

beginner

Give an example scenario where event-driven architecture is preferred.

When many services need to react to changes independently, like updating inventory, sending notifications, and logging after a purchase, event-driven is preferred.

Which architecture involves services sending direct requests and waiting for responses?

A Event-driven

B Request-driven

C Batch processing

D Peer-to-peer

Request-driven architecture uses direct calls where one service waits for another's response.

In event-driven architecture, how do services communicate?

A By reacting to events asynchronously

B By polling each other continuously

C By sharing a common database

D By sending synchronous requests

Services react to events asynchronously without waiting for immediate responses.

What is a main advantage of event-driven systems?

A Better scalability and fault tolerance

B Tight coupling between services

C Synchronous communication

D Simpler debugging

Event-driven systems allow services to scale independently and handle failures gracefully.

Which problem is common in request-driven microservices?

A Services never communicate

B Services are loosely coupled

C Services wait and block on responses

D Services use events to communicate

Request-driven services often wait for responses, causing delays or blocking.

When is event-driven architecture most useful?

A When services never communicate

B When immediate response is required

C When services share a single database

D When services must act independently on changes

Event-driven is best when services react independently to events without waiting.

Explain the differences between event-driven and request-driven architectures in microservices.

Think about how services talk and wait for each other.

Describe a real-world example where event-driven architecture improves system design over request-driven.

Consider systems with many independent reactions to one action.