<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Cloud - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Cloud Articles feed</description>
    <item>
      <title>Article: When a Cloud Region Fails: Rethinking High Availability in a Geopolitically Unstable World</title>
      <link>https://www.infoq.com/articles/sovereign-fault-domains-cloud-resilience/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Cloud-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/sovereign-fault-domains-cloud-resilience/en/headerimage/sovereign-fault-domains-cloud-resilience-header-1776430533702.jpg"/&gt;&lt;p&gt;Sovereign fault domains are failure boundaries defined by legal, political, or physical jurisdiction rather than hardware topology. The article maps geopolitical events to known distributed-systems failure modes, argues multi-region should replace multi-AZ as the HA baseline for systems crossing jurisdictions, and outlines design patterns, chaos experiments, and an ALE model to justify the spend.&lt;/p&gt; &lt;i&gt;By Rohan Vardhan&lt;/i&gt;</description>
      <category>Site Reliability Engineering</category>
      <category>Chaos Engineering</category>
      <category>Fault Tolerance</category>
      <category>Reliability</category>
      <category>Architecture</category>
      <category>Availability</category>
      <category>Disaster Recovery</category>
      <category>Cloud</category>
      <category>Resilience</category>
      <category>Cloud Architecture</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>article</category>
      <pubDate>Wed, 22 Apr 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/sovereign-fault-domains-cloud-resilience/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Cloud-articles</guid>
      <dc:creator>Rohan Vardhan</dc:creator>
      <dc:date>2026-04-22T09:00:00Z</dc:date>
      <dc:identifier>/articles/sovereign-fault-domains-cloud-resilience/en</dc:identifier>
    </item>
    <item>
      <title>Article: Using AWS Lambda Extensions to Run Post-Response Telemetry Flush</title>
      <link>https://www.infoq.com/articles/lambda-extension-deferred-flush/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Cloud-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/lambda-extension-deferred-flush/en/headerimage/lambda-extension-deferred-flush-header-1775648097720.jpg"/&gt;&lt;p&gt;At Lead Bank, synchronous telemetry flushing caused intermittent exporter stalls to become user-facing 504 gateway timeouts. By leveraging AWS Lambda's Extensions API and goroutine chaining in Go, flush work is moved off the response path, returning responses immediately while preserving full observability without telemetry loss.&lt;/p&gt; &lt;i&gt;By Melvin Philips&lt;/i&gt;</description>
      <category>Serverless</category>
      <category>API Gateway</category>
      <category>AWS</category>
      <category>API</category>
      <category>HTTP</category>
      <category>Cloud</category>
      <category>AWS Lambda</category>
      <category>Development</category>
      <category>DevOps</category>
      <category>article</category>
      <pubDate>Wed, 15 Apr 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/lambda-extension-deferred-flush/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Cloud-articles</guid>
      <dc:creator>Melvin Philips</dc:creator>
      <dc:date>2026-04-15T09:00:00Z</dc:date>
      <dc:identifier>/articles/lambda-extension-deferred-flush/en</dc:identifier>
    </item>
  </channel>
</rss>
