<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>System-Design on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/system-design/</link>
		<description>Recent content in System-Design on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Mon, 20 Jul 2026 18:45:00 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/system-design/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 second representation of data placed closer to a reader or cheaper execution path. It can reduce latency and origin load, but it also introduces another state boundary that can be empty, stale, unavailable, or inconsistent with the source of truth. Good cache design therefore starts with workload and correctness requirements, not with a product selection or a target hit ratio.&lt;/p&gt;&#xA;&lt;p&gt;&lt;figure&gt;&#xA;    &lt;img src=&#34;https://www.compilemymind.com/posts/system-design-caching-cache-aside-expiration-invalidation/concept-flow.svg&#34; alt=&#34;Cache-aside lifecycle, expiration, and invalidation flow&#34; width=&#34;1200&#34; height=&#34;830&#34; loading=&#34;lazy&#34; decoding=&#34;async&#34;&gt;&#xA;    &#xA;  &lt;/figure&gt;&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
