Rest API - Caching Strategies
You want to design a cache invalidation strategy for a REST API where data changes frequently but must stay fresh within 5 minutes. Which combined strategy is best?
You want to design a cache invalidation strategy for a REST API where data changes frequently but must stay fresh within 5 minutes. Which combined strategy is best?
hard📝 Application Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Analyze freshness requirement
Data must be fresh within 5 minutes, so time-based expiry should be 5 minutes or less.Step 2: Combine with event-based invalidation
Event-based invalidation clears cache immediately on data changes, improving freshness.Step 3: Evaluate other options
Manual invalidation is slow, versioning alone may keep stale data, and 1-hour expiry is too long.Final Answer:
Use time-based invalidation with 5-minute expiry plus event-based invalidation on data changes -> Option AQuick Check:
Combine time and event for fresh cache [OK]
Quick Trick: Combine time and event for best freshness [OK]
Common Mistakes:
MISTAKES- Relying only on manual invalidation
- Using too long expiry times
- Ignoring event triggers for changes
Master "Caching Strategies" in Rest API
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Rest API Quizzes