<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Memcached on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/memcached/</link>
    <description>Recent content in Memcached on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 25 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/memcached/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Twemproxy vs Mcrouter vs Envoy: Self-Hosted Cache Proxy Guide 2026</title>
      <link>https://www.pistack.xyz/posts/2026-04-25-twemproxy-vs-mcrouter-vs-envoy-self-hosted-cache-proxy-guide-2026/</link>
      <pubDate>Sat, 25 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-04-25-twemproxy-vs-mcrouter-vs-envoy-self-hosted-cache-proxy-guide-2026/</guid>
      <description>&lt;p&gt;When you run a single Redis or Memcached instance, everything works fine — until it doesn&amp;rsquo;t. As traffic grows, you need to shard across multiple cache backends, pool connections efficiently, and handle failover without application changes. That&amp;rsquo;s where a cache proxy sits between your services and your cache layer, transparently managing routing, sharding, and resilience.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
