Fallback pattern in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Fallback pattern in microservices?

The Fallback pattern is a design approach where a system provides an alternative response or behavior when a service call fails or is unavailable, ensuring the system remains responsive and stable.

beginner

Why is the Fallback pattern important in distributed systems?

Because services can fail or be slow, the Fallback pattern helps prevent cascading failures by providing a backup response, improving system reliability and user experience.

intermediate

Name two common types of fallback strategies.

1. Returning a default or cached response.<br>2. Calling a backup service or a simpler version of the service.

intermediate

How does the Fallback pattern relate to the Circuit Breaker pattern?

The Circuit Breaker detects failures and stops calls to a failing service temporarily, while the Fallback pattern provides an alternative response during that time to keep the system responsive.

beginner

What is a risk of not implementing a Fallback pattern in microservices?

Without fallback, a failure in one service can cause delays or failures in others, leading to poor user experience or system crashes.

What does the Fallback pattern do when a service call fails?

A Retries the call indefinitely

B Provides an alternative response or behavior

C Shuts down the entire system

D Ignores the failure and continues

The Fallback pattern provides an alternative response or behavior to keep the system responsive when a service call fails.

Which of the following is NOT a common fallback strategy?

A Returning cached data

B Calling a backup service

C Returning a default response

D Increasing the timeout indefinitely

Increasing the timeout indefinitely is not a fallback strategy; it can cause delays and worsen failures.

How does the Fallback pattern improve user experience?

A By shutting down services to prevent errors

B By hiding all errors from users

C By providing quick alternative responses during failures

D By logging errors silently

Fallback provides quick alternative responses so users do not face long delays or errors.

Which pattern often works together with Fallback to handle service failures?

A Circuit Breaker

B Load Balancer

C Singleton

D Observer

Circuit Breaker detects failures and stops calls temporarily, while Fallback provides alternative responses.

What is a potential consequence of not using fallback in microservices?

A Cascading failures and poor system stability

B Faster response times

C Reduced system complexity

D Automatic error correction

Without fallback, failures can cascade causing instability and poor user experience.

Explain the Fallback pattern and why it is important in microservices.

Think about what happens when a service is down and how fallback helps.

Describe how the Fallback pattern works together with the Circuit Breaker pattern.

Consider how these patterns prevent failures from spreading.