<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Are enterprises moving from &amp;quot;Data Lakehouse&amp;quot; to &amp;quot;Agentic Lakehouse&amp;quot;? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/are-enterprises-moving-from-quot-data-lakehouse-quot-to-quot/m-p/163205#M55111</link>
    <description>&lt;P class=""&gt;Introduction several capabilities that seem to shift Databricks from being primarily a data platform to becoming an AI operating system—Genie One, Agent Bricks, AI Gateway, Lakebase Search, and business semantics.&lt;/P&gt;&lt;P class=""&gt;Do you see the future enterprise architecture evolving from:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Data Sources → Lakehouse → BI&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;to&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Data Sources → Lakehouse → Agents → Business Users&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;If you're already building production AI solutions on Databricks, what architectural changes are you making after these announcements?&lt;/P&gt;&lt;P&gt;I'd love to hear perspectives from architects, platform engineers, and the Databricks product team.&lt;/P&gt;</description>
    <pubDate>Thu, 16 Jul 2026 15:39:59 GMT</pubDate>
    <dc:creator>Bitrip007</dc:creator>
    <dc:date>2026-07-16T15:39:59Z</dc:date>
    <item>
      <title>Are enterprises moving from "Data Lakehouse" to "Agentic Lakehouse"?</title>
      <link>https://community.databricks.com/t5/data-engineering/are-enterprises-moving-from-quot-data-lakehouse-quot-to-quot/m-p/163205#M55111</link>
      <description>&lt;P class=""&gt;Introduction several capabilities that seem to shift Databricks from being primarily a data platform to becoming an AI operating system—Genie One, Agent Bricks, AI Gateway, Lakebase Search, and business semantics.&lt;/P&gt;&lt;P class=""&gt;Do you see the future enterprise architecture evolving from:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Data Sources → Lakehouse → BI&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;to&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Data Sources → Lakehouse → Agents → Business Users&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;If you're already building production AI solutions on Databricks, what architectural changes are you making after these announcements?&lt;/P&gt;&lt;P&gt;I'd love to hear perspectives from architects, platform engineers, and the Databricks product team.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jul 2026 15:39:59 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/are-enterprises-moving-from-quot-data-lakehouse-quot-to-quot/m-p/163205#M55111</guid>
      <dc:creator>Bitrip007</dc:creator>
      <dc:date>2026-07-16T15:39:59Z</dc:date>
    </item>
    <item>
      <title>Re: Are enterprises moving from "Data Lakehouse" to "Agentic Lakehouse"?</title>
      <link>https://community.databricks.com/t5/data-engineering/are-enterprises-moving-from-quot-data-lakehouse-quot-to-quot/m-p/164087#M55228</link>
      <description>&lt;P&gt;Yes its true. I work in an AdTech and MarTech company where we serve customers with rich AdTech use cases like Campaign Optimization, Creative Performance, AdOps etc.,&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the recent past we have seen multiple use cases with several customers asking for Agentic AI Solutions.&lt;/P&gt;</description>
      <pubDate>Sat, 25 Jul 2026 13:20:49 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/are-enterprises-moving-from-quot-data-lakehouse-quot-to-quot/m-p/164087#M55228</guid>
      <dc:creator>suryaprayaga</dc:creator>
      <dc:date>2026-07-25T13:20:49Z</dc:date>
    </item>
  </channel>
</rss>

