Event-driven vs request-driven in Microservices - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding communication style in microservices

Which statement best describes the main difference between event-driven and request-driven communication in microservices?

A Event-driven uses asynchronous messages to notify changes, while request-driven uses synchronous calls expecting immediate responses.

B Event-driven requires direct calls between services, while request-driven uses message queues.

C Request-driven communication is always asynchronous, while event-driven is always synchronous.

D Event-driven communication does not support decoupling, while request-driven does.

💡 Hint

Think about how services interact and wait for responses.

Event-driven communication is asynchronous and decouples services by sending events without waiting for immediate replies. Request-driven communication is synchronous, where one service calls another and waits for a response.

❓ Architecture

intermediate

Choosing communication style for a payment system

You are designing a payment processing microservice that must confirm payment success before updating the order status. Which communication style is most suitable?

A Event-driven, because it allows the payment service to notify order service asynchronously after processing.

B Event-driven, because it guarantees immediate response from payment service.

C Request-driven, because the order service needs immediate confirmation to update status synchronously.

D Request-driven, because it avoids any communication between services.

💡 Hint

Consider if the order service needs to wait for payment confirmation before proceeding.

Since the order service must update status only after payment confirmation, synchronous request-driven communication is suitable to get immediate response. Event-driven is asynchronous and may delay confirmation.

❓ scaling

advanced

Scaling microservices with event-driven architecture

Which advantage does event-driven architecture provide when scaling microservices under high load?

A It eliminates the need for message brokers, reducing infrastructure complexity.

B It forces all services to wait for each other, reducing concurrency issues.

C It requires synchronous calls that simplify load balancing.

D It allows services to process events independently and at their own pace, improving scalability and fault tolerance.

💡 Hint

Think about how asynchronous processing affects service independence and load handling.

Event-driven architecture decouples services so they can consume and process events independently, which helps handle high load by scaling services separately and improving fault tolerance.

❓ tradeoff

advanced

Tradeoffs between event-driven and request-driven communication

What is a key tradeoff when choosing event-driven communication over request-driven in microservices?

A Event-driven improves decoupling but can make debugging and tracing harder due to asynchronous flows.

B Event-driven guarantees immediate responses but increases coupling between services.

C Request-driven communication eliminates the need for service discovery.

D Request-driven communication is always faster and more scalable than event-driven.

💡 Hint

Consider how asynchronous communication affects system observability.

Event-driven communication decouples services but introduces complexity in tracing and debugging because events flow asynchronously and may be processed later, making it harder to track the full request path.

❓ estimation

expert

Estimating message volume in event-driven microservices

A microservice emits an event for every user action. If the system has 10,000 users each performing 5 actions per minute, estimate the number of events generated per hour.

A 30,000 events per hour

B 3,000,000 events per hour

C 300,000 events per hour

D 600,000 events per hour

💡 Hint

Calculate total actions per minute and multiply by 60 minutes.

10,000 users * 5 actions/minute = 50,000 events per minute. Over 60 minutes: 50,000 * 60 = 3,000,000 events per hour.