Graceful degradation in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Graceful Degradation in Microservices

Which of the following best describes the concept of graceful degradation in a microservices architecture?

A The system shuts down completely to avoid inconsistent states when any service fails.

B The system continues to operate with reduced functionality when some services fail.

C The system automatically scales up all services to prevent any failure.

D The system ignores failures and retries indefinitely without fallback.

💡 Hint

Think about how a system behaves when parts of it stop working but the whole does not fail.

Graceful degradation means the system keeps working with limited features instead of failing completely.

❓ Architecture

intermediate

Designing a Graceful Degradation Strategy

You are designing a microservices system for an online store. Which architectural approach best supports graceful degradation when the payment service is down?

A Allow users to place orders but queue payments for later processing.

B Block all order placements until the payment service is fully operational.

C Automatically cancel all orders if payment service is unavailable.

D Redirect users to a static error page without any order options.

💡 Hint

Consider how to keep the core functionality available even if payment is temporarily unavailable.

Queuing payments allows the system to accept orders and process payments later, maintaining user experience despite partial failure.

❓ scaling

advanced

Scaling Considerations for Graceful Degradation

In a microservices system, which scaling strategy best supports graceful degradation during high load on a critical service?

A Ignore load and let the service fail to force a restart.

B Increase the number of requests sent to the overloaded service to speed up processing.

C Disable all other services to focus resources on the overloaded service.

D Implement circuit breakers to temporarily stop requests to the overloaded service and fallback to cached data.

💡 Hint

Think about how to protect a service under stress while still providing some response.

Circuit breakers prevent cascading failures by stopping calls to failing services and providing fallback responses, enabling graceful degradation.

❓ tradeoff

advanced

Trade-offs in Graceful Degradation Design

What is a common trade-off when implementing graceful degradation in microservices?

A Reduced feature availability in exchange for higher system availability.

B Increased feature complexity with no impact on system availability.

C Complete system shutdown to ensure data consistency.

D Unlimited retries causing increased latency but no feature loss.

💡 Hint

Consider what the system sacrifices to keep running during partial failures.

Graceful degradation often means some features are limited or disabled to keep the system running smoothly.

❓ estimation

expert

Estimating Impact of Graceful Degradation on User Experience

A microservices system has 10 services. If 2 services degrade gracefully by reducing functionality, what percentage of total services are fully operational?

A 60%

B 20%

C 80%

D 100%

💡 Hint

Calculate the number of services fully operational versus total services.

If 2 out of 10 services degrade, 8 remain fully operational, which is 80%.