<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>high availability architecture on Kuldeep Pisda</title><link>https://kdpisda.in/tag/high-availability-architecture/</link><description>Recent content in high availability architecture on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 26 Nov 2025 12:26:15 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/high-availability-architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>High Availability Architecture That Actually Works</title><link>https://kdpisda.in/high-availability-architecture-that-actually-works/</link><pubDate>Wed, 26 Nov 2025 12:26:15 +0530</pubDate><guid>https://kdpisda.in/high-availability-architecture-that-actually-works/</guid><description>&lt;p&gt;It always starts with that frantic 3 AM alert: &lt;em&gt;&amp;lsquo;The site is down.&amp;rsquo;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;We have all been there. That sinking feeling as you scramble to figure out what just broke is a rite of passage for many of us in the industry. I still remember the cold sweat from my first major production outage; it felt like the entire internet was staring at me.&lt;/p&gt;
&lt;p&gt;This guide is for every engineer who has stared at that error screen and vowed, &amp;ldquo;never again.&amp;rdquo; We are not talking about abstract theory here; we are talking about practical, battle tested high availability architecture that keeps your services running, your users happy, and most importantly, lets you get a good night&amp;rsquo;s sleep.&lt;/p&gt;</description></item></channel></rss>