<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Caching on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/caching/</link>
    <description>Recent content in Caching on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 27 Mar 2024 11:47:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/caching/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cache Design as a Reliability Practice, Not an Optimisation</title>
      <link>https://blog.turboawesome.win/2024/03/cache-design-as-a-reliability-practice-not-an-optimisation/</link>
      <pubDate>Wed, 27 Mar 2024 11:47:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2024/03/cache-design-as-a-reliability-practice-not-an-optimisation/</guid>
      <description>Most engineers add caches to make things faster. At scale, the more important reason to design caches carefully is reliability — a cache failure should not cascade into a system failure. The patterns that prevent that are different from the patterns that optimise for speed.</description>
    </item>
  </channel>
</rss>
