<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>System-Design on cloudmato.com</title><link>https://cloudmato.com/tags/system-design/</link><description>Recent content in System-Design on cloudmato.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>cloudmato.com</managingEditor><webMaster>cloudmato.com</webMaster><lastBuildDate>Tue, 09 Jun 2026 18:38:02 +0530</lastBuildDate><atom:link href="https://cloudmato.com/tags/system-design/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Redis? History, Use Cases &amp; Best Alternatives</title><link>https://cloudmato.com/posts/why-use-redis-history-alternatives/</link><pubDate>Tue, 09 Jun 2026 18:38:02 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/why-use-redis-history-alternatives/</guid><description>&lt;p&gt;&amp;ldquo;Just cache it in Redis&amp;rdquo; — you&amp;rsquo;ve probably heard that in a code review, a system design interview, or a Stack Overflow comment. It&amp;rsquo;s almost a reflex at this point. But why Redis specifically? Why not a regular database with a good index, or any other in-memory store? I dug into the history, the architecture, and the current landscape of alternatives, and the story is genuinely more interesting than the meme lets on.&lt;/p&gt;</description></item><item><title>Why Not Just Use One WebSocket Per Page Instead of HTTP?</title><link>https://cloudmato.com/posts/websocket-vs-http-one-socket-per-page/</link><pubDate>Mon, 08 Jun 2026 13:36:02 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/websocket-vs-http-one-socket-per-page/</guid><description>&lt;p&gt;I get why this question keeps coming up. A WebSocket stays open, remembers who you are, and lets the server push data to you without you asking for it again and again. So why are we still firing off a hundred separate HTTP requests for a single page load when we could just open one persistent pipe and be done with it? Honestly, the question sounds smarter than most people give it credit for — and the answer is not &amp;ldquo;because HTTP is better.&amp;rdquo; It&amp;rsquo;s a lot more nuanced than that.&lt;/p&gt;</description></item></channel></rss>