<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Architecture &amp; Design - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Architecture &amp; Design Articles feed</description>
    <item>
      <title>Article: Lakehouse Tower of Babel: Handling Identifier Resolution Rules Across Database Engines</title>
      <link>https://www.infoq.com/articles/lakehouse-sql-identifier-rules/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/lakehouse-sql-identifier-rules/en/headerimage/lakehouse-sql-identifier-rules-header-1776241856705.jpg"/&gt;&lt;p&gt;Lakehouse architectures enable multiple engines to operate on shared data using open table formats such as Apache Iceberg. However, differences in SQL identifier resolution and catalog naming rules create interoperability failures. This article examines these behaviors and explains why enforcing consistent naming conventions and cross-engine validation is critical.&lt;/p&gt; &lt;i&gt;By Maninder Parmar&lt;/i&gt;</description>
      <category>Database</category>
      <category>Data Portability</category>
      <category>SQL</category>
      <category>Data Lake</category>
      <category>Data Catalog</category>
      <category>Apache Iceberg</category>
      <category>Architecture &amp; Design</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>article</category>
      <pubDate>Fri, 17 Apr 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/lakehouse-sql-identifier-rules/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design-articles</guid>
      <dc:creator>Maninder Parmar</dc:creator>
      <dc:date>2026-04-17T09:00:00Z</dc:date>
      <dc:identifier>/articles/lakehouse-sql-identifier-rules/en</dc:identifier>
    </item>
    <item>
      <title>Article: Building Hierarchical Agentic RAG Systems: Multi-Modal Reasoning with Autonomous Error Recovery</title>
      <link>https://www.infoq.com/articles/building-hierarchical-agentic-rag-systems/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/building-hierarchical-agentic-rag-systems/en/headerimage/building-hierarchical-agentic-rag-systems-header-1775040657142.jpg"/&gt;&lt;p&gt;In this article, the author explores how hierarchical agentic RAG systems coordinate specialized workers through structured orchestration to improve accuracy, reliability, and explainability in complex enterprise analytics workflows. The article uses Protocol-H as a to show how deterministic routing, reflective retry, and modality-aware reasoning support safer multi-source query execution.&lt;/p&gt; &lt;i&gt;By Abhijit Ubale&lt;/i&gt;</description>
      <category>Retrieval-Augmented Generation</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>article</category>
      <pubDate>Thu, 09 Apr 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/building-hierarchical-agentic-rag-systems/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design-articles</guid>
      <dc:creator>Abhijit Ubale</dc:creator>
      <dc:date>2026-04-09T09:00:00Z</dc:date>
      <dc:identifier>/articles/building-hierarchical-agentic-rag-systems/en</dc:identifier>
    </item>
    <item>
      <title>Article: Stateful Continuation for AI Agents: Why Transport Layers Now Matter</title>
      <link>https://www.infoq.com/articles/ai-agent-transport-layer/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/ai-agent-transport-layer/en/headerimage/ai-agent-transport-layer-header-1775031603285.jpg"/&gt;&lt;p&gt;Agent workflows make transport a first-order concern. Multi-turn, tool-heavy loops amplify overhead that is negligible in single-turn LLM use. Stateful continuation cuts overhead dramatically. Caching context server-side can reduce client-sent data by 80%+ and improve execution time by 15–29% .&lt;/p&gt; &lt;i&gt;By Anirudh Mendiratta&lt;/i&gt;</description>
      <category>OpenAI</category>
      <category>WebSocket</category>
      <category>AI Coding</category>
      <category>HTTP</category>
      <category>AI Assisted Coding</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>article</category>
      <pubDate>Wed, 08 Apr 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/ai-agent-transport-layer/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design-articles</guid>
      <dc:creator>Anirudh Mendiratta</dc:creator>
      <dc:date>2026-04-08T09:00:00Z</dc:date>
      <dc:identifier>/articles/ai-agent-transport-layer/en</dc:identifier>
    </item>
  </channel>
</rss>
