Why events decouple services in Microservices - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How do events help decouple microservices?

Imagine two microservices: Service A and Service B. Service A sends an event when it finishes a task. How does this event help decouple Service A from Service B?

A Service B directly calls Service A's functions to get data.

B Service A waits for Service B to confirm it received the event before continuing.

C Service A sends the event and continues without knowing if Service B received it.

D Service A and Service B share the same database to communicate.

💡 Hint

Think about how events allow services to work independently without waiting.

Events let Service A send messages without waiting for Service B. This means Service A and B do not depend on each other’s availability, reducing tight coupling.

❓ Architecture

intermediate

Which architecture pattern best shows event decoupling?

Which architecture pattern best demonstrates how events decouple services?

A Synchronous REST API calls between services.

B Shared database accessed by all services.

C Monolithic application with internal modules.

D Event-driven architecture with message broker.

💡 Hint

Think about which pattern uses events to communicate asynchronously.

Event-driven architecture uses a message broker to send events asynchronously, allowing services to operate independently and decoupled.

❓ scaling

advanced

How do events improve scalability in microservices?

When microservices communicate via events, how does this improve scalability?

A Services can process events independently and in parallel, improving throughput.

B Events force services to scale together, increasing resource use.

C Services block until events are processed, limiting throughput.

D Events require services to share resources, reducing scalability.

💡 Hint

Consider how asynchronous processing affects service load.

Events allow services to handle messages independently and at their own pace, enabling parallel processing and better scalability.

❓ tradeoff

advanced

What is a tradeoff of using events to decouple services?

Using events to decouple services has benefits but also tradeoffs. Which is a common tradeoff?

A Services become synchronous and block each other.

B It can be harder to track the flow of data and debug issues.

C Tight coupling between services increases.

D Services must share the same database schema.

💡 Hint

Think about what happens when communication is asynchronous and indirect.

Because events are asynchronous and indirect, it can be challenging to trace data flow and debug problems across services.

❓ estimation

expert

Estimate event throughput for decoupled services

A system has 5 microservices communicating via events. Each service produces 100 events per second. If the message broker can handle 400 events per second, what is the maximum sustainable event throughput without delays?

A 400 events per second

B 200 events per second

C 500 events per second

D 100 events per second

💡 Hint

Consider the total events produced and the broker's capacity.

Each of the 5 services produces 100 events per second, totaling 500 events per second. The broker can only handle 400 events per second, so the maximum sustainable throughput without delays is 400 events per second (by throttling production).