<?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 Delta Live Tables (DLT) in a production environment in Get Started Discussions</title>
    <link>https://community.databricks.com/t5/get-started-discussions/delta-live-tables-dlt-in-a-production-environment/m-p/50719#M6093</link>
    <description>&lt;P&gt;I’m keen to learn more about employing Distributed Ledger Technology (DLT) in a production environment. Databricks is indeed promoting Delta Live Tables (DLT) as a comprehensive framework for creating robust, maintainable, and testable data processing pipelines.&lt;/P&gt;&lt;P&gt;In our recent project, we've opted to use DLT to construct the bronze layer within a Medallion architecture. Our main concern comes from DLT’s lifecycle being closely tied to its associated data. Specifically, if a DLT pipeline is deleted, all the linked data risks being erased as well. Clearly, no customer can afford to lose months of valuable data due to a single error.&lt;/P&gt;&lt;P&gt;I’m interested to know how others are managing this scenario. Are there efficient recovery procedures in place to handle accidental deletions of a DLT pipeline? Any shared experiences or recommendations would be greatly appreciated."&lt;/P&gt;&lt;P&gt;&lt;!--  notionvc: 005d415e-b009-4d64-b29e-590f376fadd9  --&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 09 Nov 2023 09:22:13 GMT</pubDate>
    <dc:creator>serelk</dc:creator>
    <dc:date>2023-11-09T09:22:13Z</dc:date>
    <item>
      <title>Delta Live Tables (DLT) in a production environment</title>
      <link>https://community.databricks.com/t5/get-started-discussions/delta-live-tables-dlt-in-a-production-environment/m-p/50719#M6093</link>
      <description>&lt;P&gt;I’m keen to learn more about employing Distributed Ledger Technology (DLT) in a production environment. Databricks is indeed promoting Delta Live Tables (DLT) as a comprehensive framework for creating robust, maintainable, and testable data processing pipelines.&lt;/P&gt;&lt;P&gt;In our recent project, we've opted to use DLT to construct the bronze layer within a Medallion architecture. Our main concern comes from DLT’s lifecycle being closely tied to its associated data. Specifically, if a DLT pipeline is deleted, all the linked data risks being erased as well. Clearly, no customer can afford to lose months of valuable data due to a single error.&lt;/P&gt;&lt;P&gt;I’m interested to know how others are managing this scenario. Are there efficient recovery procedures in place to handle accidental deletions of a DLT pipeline? Any shared experiences or recommendations would be greatly appreciated."&lt;/P&gt;&lt;P&gt;&lt;!--  notionvc: 005d415e-b009-4d64-b29e-590f376fadd9  --&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Nov 2023 09:22:13 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/delta-live-tables-dlt-in-a-production-environment/m-p/50719#M6093</guid>
      <dc:creator>serelk</dc:creator>
      <dc:date>2023-11-09T09:22:13Z</dc:date>
    </item>
    <item>
      <title>Re: Delta Live Tables (DLT) in a production environment</title>
      <link>https://community.databricks.com/t5/get-started-discussions/delta-live-tables-dlt-in-a-production-environment/m-p/50723#M6094</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Just a small remark: I definitely meant Delta Live Tables, not Distributed Ledger Technology (DLT)&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Nov 2023 10:02:53 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/delta-live-tables-dlt-in-a-production-environment/m-p/50723#M6094</guid>
      <dc:creator>serelk</dc:creator>
      <dc:date>2023-11-09T10:02:53Z</dc:date>
    </item>
  </channel>
</rss>

