<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data-Structures on cloudmato.com</title><link>https://cloudmato.com/tags/data-structures/</link><description>Recent content in Data-Structures on cloudmato.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>cloudmato.com</managingEditor><webMaster>cloudmato.com</webMaster><lastBuildDate>Thu, 25 Jun 2026 11:33:38 +0530</lastBuildDate><atom:link href="https://cloudmato.com/tags/data-structures/index.xml" rel="self" type="application/rss+xml"/><item><title>Build Redis From Scratch: Data Structures &amp; System Design</title><link>https://cloudmato.com/posts/build-redis-from-scratch-data-structures-system-design/</link><pubDate>Thu, 25 Jun 2026 11:33:38 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/build-redis-from-scratch-data-structures-system-design/</guid><description>&lt;p&gt;Redis is one of those rare pieces of software where the source code is short enough to actually read and deep enough to teach you something new every time. I&amp;rsquo;ve spent a good amount of time going through the actual Redis source — and what strikes me every time is how deliberately every design choice was made. Nothing is accidental.&lt;/p&gt;
&lt;p&gt;So let&amp;rsquo;s actually design one from the ground up — not a toy, but an architecture that mirrors what Redis actually does. Data structures, event loop, protocol, expiry, persistence. All of it.&lt;/p&gt;</description></item></channel></rss>