<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Redis on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/redis/</link>
		<description>Recent content in Redis on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sun, 26 Jul 2026 18:30:00 +0200</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/redis/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>System Design Caching: Cache-Aside, Expiration, and Invalidation</title>
				<link>https://www.compilemymind.com/posts/system-design-caching-cache-aside-expiration-invalidation/</link>
				<pubDate>Mon, 20 Jul 2026 12:35:30 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/system-design-caching-cache-aside-expiration-invalidation/</guid>
				<description>&lt;p&gt;A cache is a copy. Every useful cache design must therefore answer a harder question than “What TTL should we use?”:&lt;/p&gt;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&lt;blockquote class=&#34;blockquote-regular&#34;&gt;&#xA;  &lt;p&gt;&lt;strong&gt;How wrong may this copy be, for how long, and what happens when the cache or origin fails?&lt;/strong&gt;&lt;/p&gt;&#xA;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;Cache-aside is popular because the application controls those answers. It is also easy to implement incompletely: a fast happy path can hide stale data, stampedes, unsafe keys, and an origin that collapses the moment Redis is unavailable.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
