<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Reliability on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/reliability/</link>
		<description>Recent content in Reliability on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Thu, 22 Oct 2026 11:30:19 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/reliability/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>High Availability vs Disaster Recovery: What Is the Difference?</title>
				<link>https://www.compilemymind.com/posts/high-availability-vs-disaster-recovery/</link>
				<pubDate>Thu, 22 Oct 2026 11:30:19 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/high-availability-vs-disaster-recovery/</guid>
				<description>&lt;p&gt;The application has three servers, a load balancer, and a database replica. One server fails, traffic moves elsewhere, and nobody notices.&lt;/p&gt;&#xA;&lt;p&gt;Then an operator deletes the wrong production data. The database faithfully replicates the deletion to every live copy.&lt;/p&gt;&#xA;&lt;p&gt;The architecture was available. It was not recoverable.&lt;/p&gt;&#xA;&lt;p&gt;That is the tension between high availability and disaster recovery. &lt;strong&gt;High availability keeps a service usable through failures the running system is designed to absorb. Disaster recovery restores an acceptable service after a larger or different disruption crosses that design boundary.&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
