Annie  Emard

Annie Emard

1625370660

Complexity of Caching: Strategy, Invalidation & Fallbacks

Caching ain’t easy! There are many factors that add to the complexity of caching. My general recommendation is to avoid caching if you can. However, caching can bring performance and scaling which you might need.

If you’re starting to use a cache in your system here are some things to think about. Adding a cache isn’t that trivial and requires some thought about caching strategies, how to invalidate, and fallbacks to your database. Caching can improve performance and scalability, but can also bring your entire system down if it’s failing.

Blog Post:
https://codeopinion.com/the-complexity-of-caching/

🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1

💥 Join this channel to get access to source code, demos, and slides!
https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join

📝 Blog: https://codeopinion.com

📚 Book Recommendations

Domain-Driven Design
https://amzn.to/2QwG8sb

Patterns of Enterprise Application Architecture
https://amzn.to/3d8kMJj

Refactoring: Improving the Design of Existing Code
https://amzn.to/2NVdP5Q

Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith
https://amzn.to/3srUuZ6

RESTful Web Clients: Enabling Reuse Through Hypermedia
https://amzn.to/3d8Q96B

0:00 Intro
0:20 Caching Strategies
2:49 Expiring
3:29 Async Messaging
4:43 Fallback Implications

CodeOpinon: https://codeopinion.com
Twitter: https://twitter.com/codeopinion

#softwarearchitecture #caching #redis

#softwarearchitecture #caching #redis

Complexity of Caching: Strategy, Invalidation & Fallbacks