Request-response vs event-driven in Microservices - Quick Revision & Key Differences

Recall & Review

beginner

What is the main characteristic of the request-response communication pattern?

In request-response, a service sends a request and waits for a direct reply from another service before continuing.

beginner

How does event-driven communication differ from request-response?

Event-driven communication uses events to notify other services asynchronously, without waiting for an immediate reply.

beginner

Give a real-life example of request-response communication.

Ordering food at a restaurant: you place an order (request) and wait for the waiter to bring your food (response).

beginner

Give a real-life example of event-driven communication.

Fire alarm system: when smoke is detected, the alarm (event) sounds and multiple systems respond independently without waiting.

intermediate

What is a key advantage of event-driven systems over request-response in microservices?

Event-driven systems improve scalability and decoupling because services do not wait for replies and can process events independently.

Which communication pattern involves waiting for a direct reply before proceeding?

A Event-driven

B Multicast

C Broadcast

D Request-response

Request-response requires the sender to wait for a reply before continuing.

In event-driven architecture, how do services communicate?

A Asynchronously through events

B Synchronously with immediate replies

C Only through direct API calls

D Using shared databases

Event-driven systems use asynchronous events to notify services without waiting.

Which pattern is better for decoupling services in microservices?

A Event-driven

B Monolithic

C Request-response

D Synchronous polling

Event-driven architecture decouples services by using asynchronous events.

What is a downside of request-response communication?

A Services do not get immediate feedback

B It can cause tight coupling and waiting delays

C It is always asynchronous

D It requires event brokers

Request-response can cause services to wait and be tightly coupled.

Which scenario fits event-driven communication best?

A Client requests data and waits for response

B User logs in and waits for confirmation

C Sensor sends data to multiple systems when triggered

D Synchronous database query

Event-driven suits scenarios where multiple systems react independently to events.

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

Think about how services wait or don't wait for answers.

Describe a real-life example for each communication pattern and how it relates to microservices.

Use everyday situations to explain technical ideas.