<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Azure</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Azure feed</description>
    <item>
      <title>Microsoft Three-Layer LLM Routing Architecture for AI Agents on AKS</title>
      <link>https://www.infoq.com/news/2026/07/microsoft-agents-aks-routing/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Azure</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/07/microsoft-agents-aks-routing/en/headerimage/generatedHeaderImage-1785241354822.jpg"/&gt;&lt;p&gt;Microsoft has released a reference architecture for routing agent traffic on Azure Kubernetes Service. It breaks down the issue into three key choices: which model answers a call, how the call is managed, and which GPU replica handles it.&lt;/p&gt; &lt;i&gt;By Claudio Masolo&lt;/i&gt;</description>
      <category>Agents</category>
      <category>Kubernetes</category>
      <category>Routing</category>
      <category>Azure</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Wed, 29 Jul 2026 12:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/07/microsoft-agents-aks-routing/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Azure</guid>
      <dc:creator>Claudio Masolo</dc:creator>
      <dc:date>2026-07-29T12:00:00Z</dc:date>
      <dc:identifier>/news/2026/07/microsoft-agents-aks-routing/en</dc:identifier>
    </item>
    <item>
      <title>Article: The Hard-Stop Rule: From 3 HCM Monoliths to 120 Domain Microservices</title>
      <link>https://www.infoq.com/articles/pull-based-migration/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Azure</link>
      <description>&lt;img src="https://res.infoq.com/articles/pull-based-migration/en/headerimage/pull-based-migration-header-1784812950594.jpg"/&gt;&lt;p&gt;A payroll and HR software team rebuilt three monoliths into over 120 smaller services over five years, with no dedicated migration budget. Every new feature was built as its own service instead of changing the old ones. The article covers the pull-based migration, the tools that made this possible, how costs were kept down, and the problems the team ran into along the way.&lt;/p&gt; &lt;i&gt;By Prashanth Pasham&lt;/i&gt;</description>
      <category>Cloud Computing</category>
      <category>Cloud</category>
      <category>Cost Optimization</category>
      <category>Azure</category>
      <category>Feature Toggle</category>
      <category>Microservices</category>
      <category>Modular Monolith</category>
      <category>Platform Engineering</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Tue, 28 Jul 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/pull-based-migration/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Azure</guid>
      <dc:creator>Prashanth Pasham</dc:creator>
      <dc:date>2026-07-28T09:00:00Z</dc:date>
      <dc:identifier>/articles/pull-based-migration/en</dc:identifier>
    </item>
  </channel>
</rss>
