<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Multi-Region on IQLAS</title>
    <link>/tags/multi-region/</link>
    <description>Recent content in Multi-Region on IQLAS</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 11 Apr 2026 17:17:57 +0530</lastBuildDate>
    <atom:link href="/tags/multi-region/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Architecting for Scale: AWS Multi-Region Deployments Done Right</title>
      <link>/blog/architecting-for-scale-aws-multi-region-deployments-done-right/</link>
      <pubDate>Sat, 28 Feb 2026 00:00:00 +0000</pubDate>
      <guid>/blog/architecting-for-scale-aws-multi-region-deployments-done-right/</guid>
      <description>Multi-region AWS architecture is not a feature you switch on — it is a set of deliberate, difficult tradeoffs between consistency, cost, and complexity. Here is how to make those tradeoffs well.</description>
    </item>
  </channel>
</rss>
