<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - ElasticSearch - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ ElasticSearch Articles feed</description>
    <item>
      <title>Article: Optimizing Wellhub Autocomplete Service Latency: a Multi-Region Architecture</title>
      <link>https://www.infoq.com/articles/multi-region-architecture/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=ElasticSearch-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/multi-region-architecture/en/headerimage/optimizing-wellhub-autocomplete-header-1728898753118.jpg"/&gt;&lt;p&gt;Every company wants fast, reliable, and low-latency services. Achieving these goals requires significant investment and effort. In this article, I will share how Wellhub invested in a multi-region architecture to achieve a low-latency autocomplete service.&lt;/p&gt; &lt;i&gt;By Matheus Felisberto&lt;/i&gt;</description>
      <category>Cloud</category>
      <category>S3</category>
      <category>ElasticSearch</category>
      <category>Availability</category>
      <category>AWS</category>
      <category>Cloud Security</category>
      <category>Networking</category>
      <category>Amazon Web Services</category>
      <category>Search</category>
      <category>Performance</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Thu, 17 Oct 2024 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/multi-region-architecture/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=ElasticSearch-articles</guid>
      <dc:creator>Matheus Felisberto</dc:creator>
      <dc:date>2024-10-17T09:00:00Z</dc:date>
      <dc:identifier>/articles/multi-region-architecture/en</dc:identifier>
    </item>
  </channel>
</rss>
