<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Global on Ricky Moorhouse</title>
    <link>https://rickymoorhouse.uk/tags/global/</link>
    <description>Recent content in Global on Ricky Moorhouse</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Wed, 17 Sep 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rickymoorhouse.uk/tags/global/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Global Deployment with API Connect - Serving APIs Worldwide</title>
      <link>https://rickymoorhouse.uk/blog/2025/global-deployment-with-api-connect-serving-apis-worldwide/</link>
      <pubDate>Wed, 17 Sep 2025 00:00:00 +0000</pubDate>
      <guid>https://rickymoorhouse.uk/blog/2025/global-deployment-with-api-connect-serving-apis-worldwide/</guid>
      <description>&lt;h2 id=&#34;why-global-api-deployment-matters&#34;&gt;Why Global API Deployment Matters&lt;/h2&gt;&#xA;&lt;p&gt;If you have customers around the world, serving your APIs from a global footprint significantly improves their experience by reducing latency and increasing reliability. With API Connect&#39;s multi-region capabilities, you can ensure users call your APIs from locations closest to them, providing faster response times and better resilience against regional outages.&lt;/p&gt;&#xA;&lt;p&gt;In this guide, I&#39;ll walk through deploying APIs to the 6 current regions of the API Connect Multi-tenant SaaS service on AWS. At the time of writing, these regions are:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
