<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Key-Based-Cache-Expiration on Scholion</title><link>https://scholion.thluiz.com/tags/key-based-cache-expiration/</link><description>Recent content in Key-Based-Cache-Expiration on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Tue, 24 Jun 2014 10:13:35 -0300</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/key-based-cache-expiration/index.xml" rel="self" type="application/rss+xml"/><item><title>How key-based cache expiration works</title><link>https://scholion.thluiz.com/notes/how-key-based-cache-expiration-works/</link><pubDate>Tue, 24 Jun 2014 10:13:35 -0300</pubDate><guid>https://scholion.thluiz.com/notes/how-key-based-cache-expiration-works/</guid><description>The post explains key-based cache expiration as a way to avoid manual cache invalidation by making the cache key change with the object’s updated_at timestamp, so old entries become disposable and stale data is avoided.</description></item></channel></rss>