<?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: What are best practices for designing a large-scale data engineering pipeline on Databricks for in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/what-are-best-practices-for-designing-a-large-scale-data/m-p/139275#M51133</link>
    <description>&lt;P&gt;Very generic question &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; Here are general rules and best practices related to Databricks well-architected framework:&amp;nbsp;&lt;A href="https://docs.databricks.com/aws/en/lakehouse-architecture/well-architected" target="_blank"&gt;https://docs.databricks.com/aws/en/lakehouse-architecture/well-architected&lt;/A&gt;&amp;nbsp;Take a deeper look on operational excellence, reliability and performance efficiency. On the other hand, try to adopt a mediallion architecture to logically organize data&amp;nbsp;&lt;A href="https://www.databricks.com/glossary/medallion-architecture" target="_blank"&gt;https://www.databricks.com/glossary/medallion-architecture&lt;/A&gt;&amp;nbsp;and usage of Unity catalog to centrally control and governance data.&lt;/P&gt;</description>
    <pubDate>Mon, 17 Nov 2025 07:52:01 GMT</pubDate>
    <dc:creator>Coffee77</dc:creator>
    <dc:date>2025-11-17T07:52:01Z</dc:date>
    <item>
      <title>What are best practices for designing a large-scale data engineering pipeline on Databricks for real</title>
      <link>https://community.databricks.com/t5/data-engineering/what-are-best-practices-for-designing-a-large-scale-data/m-p/139265#M51128</link>
      <description>&lt;P&gt;How do you design a scalable, reliable pipeline that handles both fast/continuous data and slower bulk data in the same system?&lt;/P&gt;</description>
      <pubDate>Mon, 17 Nov 2025 06:39:52 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/what-are-best-practices-for-designing-a-large-scale-data/m-p/139265#M51128</guid>
      <dc:creator>Suheb</dc:creator>
      <dc:date>2025-11-17T06:39:52Z</dc:date>
    </item>
    <item>
      <title>Re: What are best practices for designing a large-scale data engineering pipeline on Databricks for</title>
      <link>https://community.databricks.com/t5/data-engineering/what-are-best-practices-for-designing-a-large-scale-data/m-p/139275#M51133</link>
      <description>&lt;P&gt;Very generic question &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; Here are general rules and best practices related to Databricks well-architected framework:&amp;nbsp;&lt;A href="https://docs.databricks.com/aws/en/lakehouse-architecture/well-architected" target="_blank"&gt;https://docs.databricks.com/aws/en/lakehouse-architecture/well-architected&lt;/A&gt;&amp;nbsp;Take a deeper look on operational excellence, reliability and performance efficiency. On the other hand, try to adopt a mediallion architecture to logically organize data&amp;nbsp;&lt;A href="https://www.databricks.com/glossary/medallion-architecture" target="_blank"&gt;https://www.databricks.com/glossary/medallion-architecture&lt;/A&gt;&amp;nbsp;and usage of Unity catalog to centrally control and governance data.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Nov 2025 07:52:01 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/what-are-best-practices-for-designing-a-large-scale-data/m-p/139275#M51133</guid>
      <dc:creator>Coffee77</dc:creator>
      <dc:date>2025-11-17T07:52:01Z</dc:date>
    </item>
  </channel>
</rss>

