[Solved] A microservice architecture uses graceful degradation by returning cached data when a downstream... What additional design should be added to ensure cache freshness without sacrificing availability? | Microservices

Microservices - Resilience Patterns

A microservice architecture uses graceful degradation by returning cached data when a downstream service fails. What additional design should be added to ensure cache freshness without sacrificing availability?

ABlock user requests until cache updates

BImplement background cache refresh with fallback to stale data

CClear cache on every request

DDisable cache and always call downstream service

Step-by-Step Solution

Solution:

Step 1: Understand cache freshness vs availability tradeoff
Refreshing cache in background keeps data fresh without blocking users.
Step 2: Evaluate options for availability
Disabling cache or blocking users reduces availability; clearing cache every request is inefficient.
Final Answer:
Implement background cache refresh with fallback to stale data -> Option B
Quick Check:
Background refresh + stale fallback = Freshness + availability [OK]

Quick Trick: Refresh cache in background, serve stale if needed [OK]

Common Mistakes:

MISTAKES

Disabling cache harms availability
Blocking users reduces user experience
Clearing cache wastes resources

Master "Resilience Patterns" in Microservices

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Arch Try Challenge Design Recall Scale

More Microservices Quizzes

What additional design should be added to ensure cache freshness without sacrificing availability?

Step 1: Understand cache freshness vs availability tradeoff

Step 2: Evaluate options for availability

Final Answer:

Quick Check:

Want More Practice?