<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Resilience on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/resilience/</link>
		<description>Recent content in Resilience on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sun, 12 Jul 2026 22:15:07 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/resilience/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Proving Application Resilience on Azure: A Practical Guide to Chaos Studio</title>
				<link>https://www.compilemymind.com/posts/azure-chaos-studio-application-resilience-guide/</link>
				<pubDate>Sun, 12 Jul 2026 22:15:07 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/azure-chaos-studio-application-resilience-guide/</guid>
				<description>&lt;p&gt;In cloud computing, failures are not a matter of &lt;em&gt;if&lt;/em&gt;, but &lt;em&gt;when&lt;/em&gt;. Hardware degrades, networks experience transient latency, downstream APIs experience outages, and configurations drift. Historically, organizations attempted to prevent these failures by building increasingly complex, rigid architectures. However, as cloud environments have evolved, Microsoft has championed a fundamental paradigm shift: building systems that are &lt;strong&gt;built to bounce back&lt;/strong&gt; rather than attempting to prevent every conceivable failure.&lt;/p&gt;&#xA;&lt;p&gt;This shift is the foundation of modern cloud resiliency. Rather than assuming your infrastructure is indestructible, you must design your applications to survive infrastructure degradation, self-heal, and maintain degraded functionality when dependencies fail.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
