<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Redis - vo.rs</title><link>https://vo.rs/tags/redis/</link><description>Latest from the Redis desk at vo.rs.</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Mon, 14 Apr 2025 16:08:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/redis/" rel="self" type="application/rss+xml"/><item><title>Redis as a Cache You Actually Understand</title><link>https://vo.rs/story/redis-as-a-cache-you-actually-understand/</link><description>&lt;p&gt;Half the self-hosted apps you deploy will ask for a Redis instance in their &lt;code&gt;docker-compose.yml&lt;/code&gt;, and most people give it to them the way you leave a light on in a room you never enter: it is there, it seems to help, and you have no idea what it is doing. Then one day the app starts serving stale data, or Redis eats all your memory and gets killed, and you discover that the thing you have been running for a year is a database you never learned to read. This is a shame, because Redis is one of the most comprehensible pieces of infrastructure in the whole self-hosting toolbox once you spend an afternoon with it, and understanding it turns caching from a black box into a tool you can reason about.&lt;/p&gt;</description><pubDate>Mon, 14 Apr 2025 16:08:00 +0000</pubDate></item></channel></rss>