Why advanced patterns solve edge cases in Microservices - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use the Circuit Breaker pattern in microservices?

In a microservices system, what problem does the Circuit Breaker pattern primarily solve?

A It prevents a failing service from being called repeatedly, avoiding cascading failures.

B It encrypts data between microservices for security.

C It automatically scales services based on CPU usage.

D It balances load evenly across all service instances.

💡 Hint

Think about what happens when one service is down and others keep trying to call it.

The Circuit Breaker pattern stops calls to a failing service to prevent system-wide crashes, handling edge cases of service failure gracefully.

❓ Architecture

intermediate

How does the Saga pattern handle distributed transactions?

In microservices, which statement best describes how the Saga pattern manages transactions across multiple services?

A It uses a central database to lock all resources during the transaction.

B It queues all requests and processes them sequentially to maintain consistency.

C It breaks a transaction into a series of local transactions with compensating actions on failure.

D It duplicates data across services to avoid coordination.

💡 Hint

Think about how to keep data consistent without locking everything at once.

The Saga pattern splits a distributed transaction into smaller steps, each with a compensating action to undo changes if needed, solving edge cases of partial failures.

❓ scaling

advanced

Why does the Bulkhead pattern improve system stability under load?

How does the Bulkhead pattern help microservices handle sudden spikes in traffic without crashing the entire system?

A It isolates resources for different services so one overloaded service doesn't affect others.

B It caches all requests to reduce load on services.

C It merges all services into one to simplify scaling.

D It delays requests until the system is less busy.

💡 Hint

Think about how compartments in a ship prevent sinking if one part is damaged.

Bulkhead isolates resources like threads or connections per service, so if one service is overwhelmed, others continue working, preventing total system failure.

❓ tradeoff

advanced

What is a tradeoff when using Event Sourcing in microservices?

Which statement best describes a common tradeoff when implementing Event Sourcing?

A It simplifies querying data but makes recovery harder.

B It reduces storage needs but increases network latency.

C It eliminates the need for backups but requires synchronous communication.

D It improves write performance but complicates data consistency and querying.

💡 Hint

Consider how storing all changes as events affects reading and consistency.

Event Sourcing stores all changes as events, which can speed up writes but makes querying current state and ensuring consistency more complex.

❓ estimation

expert

Estimating capacity for a microservices system using CQRS

You design a microservices system using CQRS (Command Query Responsibility Segregation). Write requests are 10% of total, queries 90%. If the system expects 10,000 total requests per second, how many write and read requests per second should you plan capacity for?

A Write: 9,000 requests/sec, Read: 1,000 requests/sec

B Write: 1,000 requests/sec, Read: 9,000 requests/sec

C Write: 5,000 requests/sec, Read: 5,000 requests/sec

D Write: 10,000 requests/sec, Read: 10,000 requests/sec

💡 Hint

Calculate 10% and 90% of total requests separately.

With 10% writes and 90% reads out of 10,000 total requests, writes are 1,000 and reads are 9,000 requests per second.