<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Architecture - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Architecture Articles feed</description>
    <item>
      <title>Article: High Availability is Not Resilience: Why Cloud Systems Fail When it Matters Most</title>
      <link>https://www.infoq.com/articles/high-availability-not-resilience-cloud/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/high-availability-not-resilience-cloud/en/headerimage/high-availability-not-resilience-cloud-header-1790670587417.jpg"/&gt;&lt;p&gt;A routine TLS 1.3 upgrade silently broke Route 53 health checks, causing a CDN to stop routing traffic to a healthy region while internal dashboards showed nothing wrong. This article examines why HA and resilience are different problems, how control-plane dependencies create invisible failure modes, and why recovery capability erodes without explicit ownership.&lt;/p&gt; &lt;i&gt;By Alexey Golev&lt;/i&gt;</description>
      <category>Cloud</category>
      <category>Availability</category>
      <category>Resilience</category>
      <category>Architecture</category>
      <category>Site Reliability Engineering</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Thu, 01 Oct 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/high-availability-not-resilience-cloud/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture-articles</guid>
      <dc:creator>Alexey Golev</dc:creator>
      <dc:date>2026-10-01T09:00:00Z</dc:date>
      <dc:identifier>/articles/high-availability-not-resilience-cloud/en</dc:identifier>
    </item>
  </channel>
</rss>
