Fallback pattern in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the purpose of fallback pattern

In a microservices architecture, what is the primary purpose of implementing a fallback pattern?

A To log all service calls for auditing purposes

B To provide an alternative response or behavior when a service call fails or is slow

C To permanently disable a service when it fails once

D To increase the number of service calls to improve throughput

💡 Hint

Think about how to keep the system responsive when a service is unavailable.

The fallback pattern helps maintain system stability by providing an alternative response or behavior when a service call fails or is slow, preventing cascading failures.

❓ Architecture

intermediate

Choosing the correct fallback implementation

You have a microservice that calls an external payment service. Sometimes the payment service is slow or unavailable. Which fallback approach is best to maintain user experience?

A Queue the payment request for later processing and inform the user of delay

B Return a cached successful payment confirmation from a previous transaction

C Retry the payment call indefinitely until it succeeds

D Return a default failure message immediately and log the error

💡 Hint

Consider user experience and system reliability when the external service is down.

Queuing the payment request for later processing and informing the user of delay keeps the system responsive and avoids blocking or indefinite retries.

❓ scaling

advanced

Scaling fallback mechanisms under high load

When a microservice experiences high load and many fallback executions, what is a key consideration to ensure the fallback system itself does not become a bottleneck?

A Increase the number of fallback responses to match the load

B Remove all fallback logic to reduce complexity

C Implement rate limiting and circuit breakers to control fallback invocation

D Disable monitoring to reduce overhead

💡 Hint

Think about controlling traffic and preventing overload.

Rate limiting and circuit breakers help control the number of fallback executions and prevent the fallback system from becoming overwhelmed.

❓ tradeoff

advanced

Tradeoffs of aggressive fallback usage

What is a potential downside of aggressively using fallback responses in a microservices system?

A It may mask real issues and delay fixing the root cause of failures

B It always improves system performance without drawbacks

C It reduces the need for monitoring and alerting

D It guarantees 100% uptime for all services

💡 Hint

Consider what happens if fallback hides problems.

Aggressive fallback usage can hide real problems, causing delays in identifying and fixing the root causes of failures.

❓ component

expert

Designing a fallback component for a microservice

You are designing a fallback component for a microservice that calls multiple downstream services. Which design choice best supports scalability and maintainability?

A Implement a centralized fallback service that handles all fallback logic for downstream calls

B Disable fallback and rely solely on retries

C Embed fallback logic directly inside each microservice's business logic without separation

D Use a shared library with configurable fallback strategies that each microservice imports

💡 Hint

Think about code reuse and flexibility across services.

A shared library with configurable fallback strategies allows consistent, reusable, and maintainable fallback logic across multiple microservices.