Why resilience prevents cascading failures in Microservices - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does circuit breaker pattern improve resilience?

In a microservices system, what is the main way the circuit breaker pattern helps prevent cascading failures?

A It stops requests to a failing service after a threshold, preventing overload on dependent services.

B It duplicates requests to multiple services to increase availability.

C It retries failed requests indefinitely to ensure success.

D It caches all responses to avoid calling any service.

💡 Hint

Think about how stopping calls to a failing service helps the system.

The circuit breaker stops calls to a failing service after failures exceed a limit, preventing the failure from spreading and overloading other services.

❓ Architecture

intermediate

Which design helps isolate failures in microservices?

Which architectural design choice best helps prevent cascading failures by isolating faults in microservices?

A Using synchronous calls between all services without timeouts.

B Sharing a single database for all microservices.

C Implementing asynchronous messaging with queues and timeouts.

D Allowing unlimited retries on failed requests.

💡 Hint

Consider how asynchronous messaging can decouple services.

Asynchronous messaging with queues and timeouts decouples services and prevents one slow or failing service from blocking others, reducing cascading failures.

❓ scaling

advanced

Estimating capacity to avoid cascading failures

If a microservice handles 1000 requests per second and has a failure rate of 5%, what is the minimum capacity the downstream service should have to avoid cascading failures assuming retries double the load?

A At least 500 requests per second capacity.

B Exactly 1000 requests per second capacity.

C At least 1500 requests per second capacity.

D At least 2000 requests per second capacity.

💡 Hint

Consider the original load plus retries doubling the requests.

With 5% failure rate and retries doubling load, the downstream service must handle original plus retry load: 1000 * 2 = 2000 requests per second.

❓ tradeoff

advanced

Tradeoff of aggressive retry policies in microservices

What is a major downside of aggressive retry policies in microservices when trying to improve resilience?

A They always guarantee faster recovery from failures.

B They can increase load and cause cascading failures by overwhelming services.

C They reduce network traffic significantly.

D They eliminate the need for circuit breakers.

💡 Hint

Think about what happens if many retries happen at once.

Aggressive retries increase load on services, which can worsen failures and cause cascading failures instead of preventing them.

❓ component

expert

Identifying the component that prevents cascading failures

In a microservices architecture, which component is primarily responsible for preventing cascading failures by isolating faults and controlling traffic flow?

A API Gateway with rate limiting and circuit breaker features.

B Database replication system.

C Logging and monitoring system.

D Load balancer distributing requests evenly.

💡 Hint

Consider which component controls request flow and handles failures.

API Gateway with rate limiting and circuit breaker features controls traffic and isolates faults, preventing cascading failures.