<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>In-Memory on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/in-memory/</link>
    <description>Recent content in In-Memory on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 19 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/in-memory/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted In-Memory Cache Libraries: golang-lru vs go-cache vs bigcache vs TinyLFU</title>
      <link>https://www.pistack.xyz/posts/2026-06-19-self-hosted-cache-libraries-golang-lru-gocache-bigcache-tinylfu/</link>
      <pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-19-self-hosted-cache-libraries-golang-lru-gocache-bigcache-tinylfu/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;In-memory caching is one of the most impactful performance optimizations available to self-hosted applications. Whether you are building a web server that caches database query results, a proxy that buffers API responses, or a monitoring system that aggregates metrics, an efficient caching layer can reduce response times by 10x or more.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
