<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Real-Time | System Design</title><link>https://system-design.devops-monk.com/tags/real-time/</link><description>In-depth system design tutorials — from zero to millions of users. Written for engineers who want to understand how large-scale systems actually work.</description><language>en-us</language><managingEditor>abhaypratap3537@gmail.com (Abhay)</managingEditor><webMaster>abhaypratap3537@gmail.com (Abhay)</webMaster><lastBuildDate>Sun, 06 Sep 2026 22:11:29 +0000</lastBuildDate><atom:link href="https://system-design.devops-monk.com/tags/real-time/index.xml" rel="self" type="application/rss+xml"/><item><title>Design Nearby Friends</title><link>https://system-design.devops-monk.com/2026/06/design-nearby-friends/</link><pubDate>Fri, 05 Jun 2026 10:00:00 +0000</pubDate><guid isPermaLink="true">https://system-design.devops-monk.com/2026/06/design-nearby-friends/</guid><author>abhaypratap3537@gmail.com (Abhay)</author><category>Case Studies</category><description>333,000 location updates a second turn into 13.3 million messages a second. Why moving people are a completely different problem from static businesses — WebSocket fan-out, Redis Pub/Sub as a routing layer, and an interactive calculator for the amplification that decides the whole design.</description><enclosure url="https://system-design.devops-monk.com/images/articles/nearby-friends.webp" type="image/webp" length="0"/><content:encoded><![CDATA[<p><img src="https://system-design.devops-monk.com/images/articles/nearby-friends.webp" alt="Design Nearby Friends" /></p><p>333,000 location updates a second turn into 13.3 million messages a second. Why moving people are a completely different problem from static businesses — WebSocket fan-out, Redis Pub/Sub as a routing layer, and an interactive calculator for the amplification that decides the whole design.</p><p><a href="https://system-design.devops-monk.com/2026/06/design-nearby-friends/">Read the full article &rarr;</a></p>]]></content:encoded></item><item><title>Design a Chat System</title><link>https://system-design.devops-monk.com/2026/06/design-chat-system/</link><pubDate>Mon, 01 Jun 2026 14:00:00 +0000</pubDate><guid isPermaLink="true">https://system-design.devops-monk.com/2026/06/design-chat-system/</guid><author>abhaypratap3537@gmail.com (Abhay)</author><category>Case Studies</category><description>Build a Messenger-style chat system for 50 million daily users. Why WebSocket beats polling, how server-assigned sequence numbers guarantee ordering, multi-device sync, presence with heartbeats, and the reconnect problems that only appear in production.</description><enclosure url="https://system-design.devops-monk.com/images/articles/chat-system.webp" type="image/webp" length="0"/><content:encoded><![CDATA[<p><img src="https://system-design.devops-monk.com/images/articles/chat-system.webp" alt="Design a Chat System" /></p><p>Build a Messenger-style chat system for 50 million daily users. Why WebSocket beats polling, how server-assigned sequence numbers guarantee ordering, multi-device sync, presence with heartbeats, and the reconnect problems that only appear in production.</p><p><a href="https://system-design.devops-monk.com/2026/06/design-chat-system/">Read the full article &rarr;</a></p>]]></content:encoded></item></channel></rss>