<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Data Lake - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Data Lake Articles feed</description>
    <item>
      <title>Article: AI Changes the Data Interface, Not the Query Engine</title>
      <link>https://www.infoq.com/articles/ai-changes-data-interface/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Data+Lake-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/ai-changes-data-interface/en/headerimage/header-1792487239242.jpg"/&gt;&lt;p&gt;This article presents a disaster-recovery analytics workflow in which an AI agent generates constrained SQL or Python, DuckDB computes reproducible facts from Parquet, and the agent interprets the results. It explains the determinism split, replayable analysis, and four signals for deciding when an embedded engine is sufficient or a managed lakehouse is justified.&lt;/p&gt; &lt;i&gt;By Peihao Yuan&lt;/i&gt;</description>
      <category>Agentic AI Architecture</category>
      <category>duckdb</category>
      <category>Data Lake</category>
      <category>Disaster Recovery</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Thu, 22 Oct 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/ai-changes-data-interface/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Data+Lake-articles</guid>
      <dc:creator>Peihao Yuan</dc:creator>
      <dc:date>2026-10-22T09:00:00Z</dc:date>
      <dc:identifier>/articles/ai-changes-data-interface/en</dc:identifier>
    </item>
    <item>
      <title>Article: When Should You Use Liquid Clustering? Benchmarking Lakehouse Layout Strategies</title>
      <link>https://www.infoq.com/articles/liquid-clustering-lakehouse-layout/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Data+Lake-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/liquid-clustering-lakehouse-layout/en/headerimage/liquid-clustering-lakehouse-layout-header-1791465984987.jpg"/&gt;&lt;p&gt;Physical data layout is one of the most consequential decisions in lakehouse engineering. The author compares Liquid Clustering, ZOrdering, and partitioning across four workload types on Delta Lake, uncovering two undocumented failure modes that likely affect production systems today and offering a decision framework for choosing the right layout strategy.&lt;/p&gt; &lt;i&gt;By Kushal Kumar Vishwakarma&lt;/i&gt;</description>
      <category>Performance Evaluation</category>
      <category>Query</category>
      <category>Data Storage</category>
      <category>Benchmark</category>
      <category>Clustering &amp; Caching</category>
      <category>Data Lake</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Mon, 12 Oct 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/liquid-clustering-lakehouse-layout/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Data+Lake-articles</guid>
      <dc:creator>Kushal Kumar Vishwakarma</dc:creator>
      <dc:date>2026-10-12T11:00:00Z</dc:date>
      <dc:identifier>/articles/liquid-clustering-lakehouse-layout/en</dc:identifier>
    </item>
  </channel>
</rss>
