<?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 Re: Low Level Design for Moving Data from Databricks A to Databricks B in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/low-level-design-for-moving-data-from-databricks-a-to-databricks/m-p/126032#M47618</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/143693"&gt;@Pratikmsbsvm&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here's a brief low-level design checklist for Delta Lake to Delta Lake data migration:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1. Security &amp;amp; Authentication&lt;/STRONG&gt;&lt;BR /&gt;- Create service principals for both environments&lt;BR /&gt;- Set up Azure Key Vault for credential management&lt;BR /&gt;- Configure IP whitelisting and VNet peering&lt;BR /&gt;- Enable private endpoints for storage accounts&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2. DataBricks Setup&lt;/STRONG&gt;&lt;BR /&gt;- Configure cross-workspace authentication&lt;BR /&gt;- Set up appropriate cluster sizing and auto-scaling&lt;BR /&gt;- Install required libraries and dependencies&lt;BR /&gt;- Configure Unity Catalog for governance&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;3. Pipeline Design&lt;/STRONG&gt;&lt;BR /&gt;- Implement incremental data loading (CDC/watermark-based)&lt;BR /&gt;- Set up proper error handling and retry logic&lt;BR /&gt;- Configure checkpointing for streaming jobs&lt;BR /&gt;- Implement data validation and quality checks&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;4. DevOps Integration&lt;/STRONG&gt;&lt;BR /&gt;- GitLab CI/CD pipelines for automated deployment&lt;BR /&gt;- Infrastructure as Code (Terraform/ARM)&lt;BR /&gt;- Environment-specific configurations (dev/test/prod)&lt;BR /&gt;- Automated testing and rollback strategies&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;5. Monitoring &amp;amp; Operations&lt;/STRONG&gt;&lt;BR /&gt;- Azure Monitor integration&lt;BR /&gt;- Pipeline failure alerts&lt;BR /&gt;- Data freshness monitoring&lt;BR /&gt;- Performance metrics tracking&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;6. Data Considerations&lt;/STRONG&gt;&lt;BR /&gt;- Schema evolution handling&lt;BR /&gt;- Partitioning strategy optimization&lt;BR /&gt;- Z-ordering for query performance&lt;BR /&gt;- Proper table versioning and retention policies&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;7. Network &amp;amp; Compliance&lt;/STRONG&gt;&lt;BR /&gt;- NSG rules for secure communication&lt;BR /&gt;- Data encryption in transit and at rest&lt;BR /&gt;- Audit logging and data lineage&lt;BR /&gt;- RBAC implementation&lt;/P&gt;&lt;P&gt;This covers the essential components for a production-ready Delta Lake migration pipeline.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 22 Jul 2025 16:27:17 GMT</pubDate>
    <dc:creator>lingareddy_Alva</dc:creator>
    <dc:date>2025-07-22T16:27:17Z</dc:date>
    <item>
      <title>Low Level Design for Moving Data from Databricks A to Databricks B</title>
      <link>https://community.databricks.com/t5/data-engineering/low-level-design-for-moving-data-from-databricks-a-to-databricks/m-p/125991#M47604</link>
      <description>&lt;P&gt;Hello Techie,&lt;/P&gt;&lt;P&gt;May someone please help me with Low level design point what all we should considered while moving data from One Delta lake instance to another delta lake.&lt;/P&gt;&lt;P&gt;For example :-&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN&gt;Service principle creation.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;IP Whitelisting.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Any gitlab / devops related support.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;SPAN&gt;Diagram :&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Pratikmsbsvm_1-1753184957933.png" style="width: 400px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/18356i89EE0251321607DA/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Pratikmsbsvm_1-1753184957933.png" alt="Pratikmsbsvm_1-1753184957933.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I am trying to Build pipeline which bring data from A to B.&lt;/P&gt;&lt;P&gt;Please help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jul 2025 11:51:01 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/low-level-design-for-moving-data-from-databricks-a-to-databricks/m-p/125991#M47604</guid>
      <dc:creator>Pratikmsbsvm</dc:creator>
      <dc:date>2025-07-22T11:51:01Z</dc:date>
    </item>
    <item>
      <title>Re: Low Level Design for Moving Data from Databricks A to Databricks B</title>
      <link>https://community.databricks.com/t5/data-engineering/low-level-design-for-moving-data-from-databricks-a-to-databricks/m-p/126032#M47618</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/143693"&gt;@Pratikmsbsvm&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here's a brief low-level design checklist for Delta Lake to Delta Lake data migration:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1. Security &amp;amp; Authentication&lt;/STRONG&gt;&lt;BR /&gt;- Create service principals for both environments&lt;BR /&gt;- Set up Azure Key Vault for credential management&lt;BR /&gt;- Configure IP whitelisting and VNet peering&lt;BR /&gt;- Enable private endpoints for storage accounts&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2. DataBricks Setup&lt;/STRONG&gt;&lt;BR /&gt;- Configure cross-workspace authentication&lt;BR /&gt;- Set up appropriate cluster sizing and auto-scaling&lt;BR /&gt;- Install required libraries and dependencies&lt;BR /&gt;- Configure Unity Catalog for governance&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;3. Pipeline Design&lt;/STRONG&gt;&lt;BR /&gt;- Implement incremental data loading (CDC/watermark-based)&lt;BR /&gt;- Set up proper error handling and retry logic&lt;BR /&gt;- Configure checkpointing for streaming jobs&lt;BR /&gt;- Implement data validation and quality checks&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;4. DevOps Integration&lt;/STRONG&gt;&lt;BR /&gt;- GitLab CI/CD pipelines for automated deployment&lt;BR /&gt;- Infrastructure as Code (Terraform/ARM)&lt;BR /&gt;- Environment-specific configurations (dev/test/prod)&lt;BR /&gt;- Automated testing and rollback strategies&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;5. Monitoring &amp;amp; Operations&lt;/STRONG&gt;&lt;BR /&gt;- Azure Monitor integration&lt;BR /&gt;- Pipeline failure alerts&lt;BR /&gt;- Data freshness monitoring&lt;BR /&gt;- Performance metrics tracking&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;6. Data Considerations&lt;/STRONG&gt;&lt;BR /&gt;- Schema evolution handling&lt;BR /&gt;- Partitioning strategy optimization&lt;BR /&gt;- Z-ordering for query performance&lt;BR /&gt;- Proper table versioning and retention policies&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;7. Network &amp;amp; Compliance&lt;/STRONG&gt;&lt;BR /&gt;- NSG rules for secure communication&lt;BR /&gt;- Data encryption in transit and at rest&lt;BR /&gt;- Audit logging and data lineage&lt;BR /&gt;- RBAC implementation&lt;/P&gt;&lt;P&gt;This covers the essential components for a production-ready Delta Lake migration pipeline.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jul 2025 16:27:17 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/low-level-design-for-moving-data-from-databricks-a-to-databricks/m-p/126032#M47618</guid>
      <dc:creator>lingareddy_Alva</dc:creator>
      <dc:date>2025-07-22T16:27:17Z</dc:date>
    </item>
  </channel>
</rss>

