API Caching Done Right

When you need to scale your API, one of the first thing that comes to developers minds is "let's just add caching" If it were only that simple. API Caching is hard. A lot of factors to consider because you're adding a whole new set of problems when adding a cache. 🔗 Kurrent (formely EventStoreDB) https://kurrent.io 🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1 💥 Join this channel to get access to a private Discord Server and any source code in my videos. 🔥 Join via Patreon https://www.patreon.com/codeopinion ✔️ Join via YouTube https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join 📝 Blog: https://codeopinion.com 👋 Twitter: https://twitter.com/codeopinion ✨ LinkedIn: https://www.linkedin.com/in/dcomartin/ 📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeopinion 0:00 What are you caching 2:16 Where is the cache 3:37 Read Model 5:01 Using the Cache 8:11 Invalidation