<?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 Comparing OneLake, Delta Lake, and Data Lake in Data Engineering</title>
    <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Comparing-OneLake-Delta-Lake-and-Data-Lake/m-p/4292969#M5272</link>
    <description>&lt;P&gt;Below is the comparison of Onelake, Deltalake and Datalake&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Aspect&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;OneLake&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Delta Lake&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Data Lake&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Definition&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;A centralized storage system within Microsoft Fabric that acts as a unified data lake for all workloads.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;An open-source storage layer built on top of data lakes that provides ACID transactions and schema enforcement.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;A centralized repository designed to store large volumes of structured, semi-structured, and unstructured data.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Primary Use Case&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Unified storage for structured, semi-structured, and unstructured data, enabling seamless access across Fabric workloads.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Optimized for handling large-scale data with capabilities like versioning, updates, and transaction control.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Long-term storage and management of raw data for analytics, reporting, and AI/ML use cases.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Architecture&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;A service-layer abstraction that consolidates data from various Fabric workloads into a single logical layer.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;An extension of the data lake concept that uses Parquet files and a transaction log for reliability and consistency.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Typically built on cloud storage systems like Azure Data Lake Storage (ADLS), Amazon S3, or Google Cloud Storage.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;ACID Transactions&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Not directly responsible for ACID compliance but supports services (e.g., Lakehouse) that may implement Delta Lake for transactions.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Fully supports ACID transactions, enabling reliable updates, inserts, and deletes on large datasets.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Does not natively support ACID transactions unless enhanced with Delta Lake or similar frameworks.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Governance &amp;amp; Security&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Built-in integration with Fabric security, compliance, and governance frameworks for centralized control.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Relies on the underlying storage system's security; additional layers can be applied via tools or platforms.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Offers basic security features like IAM roles, encryption, and network policies; governance is often added via external tools.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Data Format&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Stores data in the Delta Lake format for interoperability across Fabric services.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Uses Parquet files with an additional transaction log layer to support Delta Lake functionality.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Supports multiple formats, including CSV, JSON, Avro, ORC, and Parquet, but without transaction logs.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Scalability&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Highly scalable and designed for enterprise-level integration across analytics workloads.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Scalable for big data analytics and machine learning workloads, with specific optimizations for large datasets.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Scalable, but performance depends on how well it is structured and managed (e.g., folder structures, metadata).&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Interoperability&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Seamlessly integrates with all Fabric components, including Lakehouse, Dataflows, Warehouse, etc.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Compatible with various data processing engines like Apache Spark, Databricks, and Microsoft Fabric.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Can integrate with various tools and frameworks (e.g., Spark, Hadoop, Presto, Athena), but requires additional setup.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Versioning&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Supports Delta Lake versioning through Fabric services (e.g., Lakehouse), enabling time travel and history tracking.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Provides built-in versioning, allowing users to query historical snapshots of data.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Does not natively support versioning unless extended with Delta Lake or other technologies.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Storage Abstraction&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Logical data storage system that abstracts physical storage (e.g., Azure Blob, ADLS).&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Built on physical storage like Azure Data Lake, Amazon S3, or HDFS with a transactional layer.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;A raw storage repository for data; lacks abstraction and relies on physical storage solutions like Azure Blob or S3.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Integration with Microsoft Fabric&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Core storage layer for Fabric workloads (Lakehouse, Warehouse, Eventhouse, etc.), ensuring consistent data access.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Used within Fabric services (e.g., Lakehouse) for managing data with transactional reliability.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Can be used with Fabric, but without additional frameworks (like Delta Lake), lacks advanced functionality.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
    <pubDate>Wed, 20 Nov 2024 09:30:11 GMT</pubDate>
    <dc:creator>SuryaTejaK</dc:creator>
    <dc:date>2024-11-20T09:30:11Z</dc:date>
    <item>
      <title>Comparing OneLake, Delta Lake, and Data Lake</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Comparing-OneLake-Delta-Lake-and-Data-Lake/m-p/4292969#M5272</link>
      <description>&lt;P&gt;Below is the comparison of Onelake, Deltalake and Datalake&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Aspect&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;OneLake&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Delta Lake&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Data Lake&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Definition&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;A centralized storage system within Microsoft Fabric that acts as a unified data lake for all workloads.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;An open-source storage layer built on top of data lakes that provides ACID transactions and schema enforcement.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;A centralized repository designed to store large volumes of structured, semi-structured, and unstructured data.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Primary Use Case&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Unified storage for structured, semi-structured, and unstructured data, enabling seamless access across Fabric workloads.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Optimized for handling large-scale data with capabilities like versioning, updates, and transaction control.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Long-term storage and management of raw data for analytics, reporting, and AI/ML use cases.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Architecture&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;A service-layer abstraction that consolidates data from various Fabric workloads into a single logical layer.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;An extension of the data lake concept that uses Parquet files and a transaction log for reliability and consistency.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Typically built on cloud storage systems like Azure Data Lake Storage (ADLS), Amazon S3, or Google Cloud Storage.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;ACID Transactions&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Not directly responsible for ACID compliance but supports services (e.g., Lakehouse) that may implement Delta Lake for transactions.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Fully supports ACID transactions, enabling reliable updates, inserts, and deletes on large datasets.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Does not natively support ACID transactions unless enhanced with Delta Lake or similar frameworks.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Governance &amp;amp; Security&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Built-in integration with Fabric security, compliance, and governance frameworks for centralized control.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Relies on the underlying storage system's security; additional layers can be applied via tools or platforms.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Offers basic security features like IAM roles, encryption, and network policies; governance is often added via external tools.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Data Format&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Stores data in the Delta Lake format for interoperability across Fabric services.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Uses Parquet files with an additional transaction log layer to support Delta Lake functionality.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Supports multiple formats, including CSV, JSON, Avro, ORC, and Parquet, but without transaction logs.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Scalability&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Highly scalable and designed for enterprise-level integration across analytics workloads.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Scalable for big data analytics and machine learning workloads, with specific optimizations for large datasets.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Scalable, but performance depends on how well it is structured and managed (e.g., folder structures, metadata).&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Interoperability&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Seamlessly integrates with all Fabric components, including Lakehouse, Dataflows, Warehouse, etc.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Compatible with various data processing engines like Apache Spark, Databricks, and Microsoft Fabric.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Can integrate with various tools and frameworks (e.g., Spark, Hadoop, Presto, Athena), but requires additional setup.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Versioning&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Supports Delta Lake versioning through Fabric services (e.g., Lakehouse), enabling time travel and history tracking.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Provides built-in versioning, allowing users to query historical snapshots of data.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Does not natively support versioning unless extended with Delta Lake or other technologies.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Storage Abstraction&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Logical data storage system that abstracts physical storage (e.g., Azure Blob, ADLS).&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Built on physical storage like Azure Data Lake, Amazon S3, or HDFS with a transactional layer.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;A raw storage repository for data; lacks abstraction and relies on physical storage solutions like Azure Blob or S3.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;STRONG&gt;Integration with Microsoft Fabric&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Core storage layer for Fabric workloads (Lakehouse, Warehouse, Eventhouse, etc.), ensuring consistent data access.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Used within Fabric services (e.g., Lakehouse) for managing data with transactional reliability.&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;Can be used with Fabric, but without additional frameworks (like Delta Lake), lacks advanced functionality.&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Wed, 20 Nov 2024 09:30:11 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Comparing-OneLake-Delta-Lake-and-Data-Lake/m-p/4292969#M5272</guid>
      <dc:creator>SuryaTejaK</dc:creator>
      <dc:date>2024-11-20T09:30:11Z</dc:date>
    </item>
    <item>
      <title>Re: Comparing OneLake, Delta Lake, and Data Lake</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Comparing-OneLake-Delta-Lake-and-Data-Lake/m-p/4293337#M5280</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/838290"&gt;@SuryaTejaK&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for sharing. Nicely covered the points to the table. It would be good if you can add about performance aspects as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Srisakthi&lt;/P&gt;</description>
      <pubDate>Wed, 20 Nov 2024 12:43:24 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Comparing-OneLake-Delta-Lake-and-Data-Lake/m-p/4293337#M5280</guid>
      <dc:creator>Srisakthi</dc:creator>
      <dc:date>2024-11-20T12:43:24Z</dc:date>
    </item>
    <item>
      <title>Re: Comparing OneLake, Delta Lake, and Data Lake</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Comparing-OneLake-Delta-Lake-and-Data-Lake/m-p/4294426#M5293</link>
      <description>&lt;P&gt;OK i will definitely try to add and thank you liked it&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/782160"&gt;@Srisakthi&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Suryateja K&lt;/P&gt;</description>
      <pubDate>Thu, 21 Nov 2024 03:38:15 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Comparing-OneLake-Delta-Lake-and-Data-Lake/m-p/4294426#M5293</guid>
      <dc:creator>SuryaTejaK</dc:creator>
      <dc:date>2024-11-21T03:38:15Z</dc:date>
    </item>
    <item>
      <title>Re: Comparing OneLake, Delta Lake, and Data Lake</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Comparing-OneLake-Delta-Lake-and-Data-Lake/m-p/4294536#M5296</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/838290"&gt;@SuryaTejaK&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for the reply from Srisakthi&amp;nbsp;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for sharing about the difference between OneLake, Delta Lake, and Data Lake, it will be helpful for many people.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;BR /&gt;Yang&lt;BR /&gt;Community Support Team&lt;/P&gt;</description>
      <pubDate>Thu, 21 Nov 2024 05:31:35 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Comparing-OneLake-Delta-Lake-and-Data-Lake/m-p/4294536#M5296</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-21T05:31:35Z</dc:date>
    </item>
    <item>
      <title>Re: Comparing OneLake, Delta Lake, and Data Lake</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Comparing-OneLake-Delta-Lake-and-Data-Lake/m-p/4294547#M5297</link>
      <description>&lt;P&gt;thank you&amp;nbsp;@Anonymous&lt;/a&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Nov 2024 05:46:15 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Comparing-OneLake-Delta-Lake-and-Data-Lake/m-p/4294547#M5297</guid>
      <dc:creator>SuryaTejaK</dc:creator>
      <dc:date>2024-11-21T05:46:15Z</dc:date>
    </item>
  </channel>
</rss>

