<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Backend on Tech Blog</title>
    <link>https://yashsachdeva.com/categories/backend/</link>
    <description>Recent content in Backend on Tech Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Yash Sachdeva</copyright>
    <lastBuildDate>Thu, 02 Apr 2026 10:12:19 +0530</lastBuildDate><atom:link href="https://yashsachdeva.com/categories/backend/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>High-Concurrency Flash Sale Systems</title>
      <link>https://yashsachdeva.com/posts/high-concurrency-flash-sale-systems/</link>
      <pubDate>Thu, 02 Apr 2026 10:12:19 +0530</pubDate>
      
      <guid>https://yashsachdeva.com/posts/high-concurrency-flash-sale-systems/</guid>
      <description>&lt;h2 class=&#34;relative group&#34;&gt;Introduction&#xA;    &lt;div id=&#34;introduction&#34; class=&#34;anchor&#34;&gt;&lt;/div&gt;&#xA;    &#xA;    &lt;span&#xA;        class=&#34;absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none&#34;&gt;&#xA;        &lt;a class=&#34;text-primary-300 dark:text-neutral-700 !no-underline&#34; href=&#34;#introduction&#34; aria-label=&#34;Anchor&#34;&gt;#&lt;/a&gt;&#xA;    &lt;/span&gt;&#xA;    &#xA;&lt;/h2&gt;&#xA;&lt;p&gt;A High Concurrency flash sale system is a system that is designed to handle a large number of concurrent users who are trying to purchase a limited number of items in a short period of time.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Load Balancers and Consistent Hashing</title>
      <link>https://yashsachdeva.com/posts/load-balancers-and-consistent-hashing/</link>
      <pubDate>Sun, 29 Mar 2026 12:57:32 +0530</pubDate>
      
      <guid>https://yashsachdeva.com/posts/load-balancers-and-consistent-hashing/</guid>
      <description>&lt;p&gt;Imagine a small app where each client talks directly to a specific server, say &lt;code&gt;https://10.0.0.1:8080&lt;/code&gt;. As traffic grows, that one server becomes a bottleneck, and if it crashes, the whole app is effectively down for any client pointing at it.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>How to Cache?</title>
      <link>https://yashsachdeva.com/posts/how-to-cache/</link>
      <pubDate>Sat, 28 Mar 2026 08:42:23 +0530</pubDate>
      
      <guid>https://yashsachdeva.com/posts/how-to-cache/</guid>
      <description>&lt;p&gt;Modern APIs frequently access databases, or complex business logic that introduce significant latency and consume CPU and I/O resources. Without caching, every request pays the full cost of database queries, network calls, and computation. This can lead to slow response times and poor scalability as traffic  increases.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
