<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SRE on Nalar</title>
    <link>https://nalar.dev/tags/sre/</link>
    <description>Recent content in SRE on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/sre/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Load Shedding and Overload Protection for Cloud Services</title>
      <link>https://nalar.dev/load-shedding-and-overload-protection-for-cloud-services/</link>
      <pubDate>Wed, 02 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/load-shedding-and-overload-protection-for-cloud-services/</guid>
      <description>&lt;p&gt;Autoscaling is useful, but it is not instantaneous. Traffic can rise faster than new instances start, a dependency can slow down, or a retry storm can multiply work. When demand exceeds safe capacity, accepting every request can make the entire service slower until almost nothing completes.&lt;/p&gt;&#xA;&lt;p&gt;Load shedding is the deliberate rejection or degradation of work to keep the system inside a recoverable operating range.&lt;/p&gt;&#xA;&lt;h2 id=&#34;overload-is-often-a-queueing-problem&#34;&gt;Overload is often a queueing problem&lt;/h2&gt;&#xA;&lt;p&gt;Imagine a service that safely handles 200 concurrent requests. A downstream dependency slows from 50 ms to 2 seconds.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
