<?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: Unity Catalog for medallion architecture in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/unity-catalog-for-medallion-architecture/m-p/109726#M43373</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/148362"&gt;@mbravonxp&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;in this case the best approach is to have a single catalog per client per environment (so 9 catalogs in total).&lt;BR /&gt;In every catalog you will create bronze, silver and gold schema.&lt;BR /&gt;Additionally every catalog will have a separate storage and also, you may consider to have a separate workspace for each client for each environment.&lt;/P&gt;
&lt;P&gt;Check my answer to the similar topic on the forum:&lt;BR /&gt;&lt;A href="https://community.databricks.com/t5/community-platform-discussions/unity-catalog-implementation/td-p/84082" target="_blank" rel="noopener"&gt;https://community.databricks.com/t5/community-platform-discussions/unity-catalog-implementation/td-p/84082&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 11 Feb 2025 07:42:12 GMT</pubDate>
    <dc:creator>filipniziol</dc:creator>
    <dc:date>2025-02-11T07:42:12Z</dc:date>
    <item>
      <title>Unity Catalog for medallion architecture</title>
      <link>https://community.databricks.com/t5/data-engineering/unity-catalog-for-medallion-architecture/m-p/109477#M43328</link>
      <description>&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif" size="3"&gt;Hello community.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif" size="3"&gt;I need help to define the most suitable approach for Unity Catalog. I have the following storage architecture in Azure Data Lake Storage.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;FONT face="arial,helvetica,sans-serif" size="3"&gt;&lt;SPAN&gt;I have data from different clients&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT face="arial,helvetica,sans-serif" size="3"&gt;&lt;SPAN&gt;I work with 3 different environments for each client: dev, pre, pro&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT face="arial,helvetica,sans-serif" size="3"&gt;&lt;SPAN&gt;I need to implement a medallion architecture, bronze, silver and gold for each environment&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif" size="3"&gt;&lt;SPAN&gt;I need to read, write and work with the Data from Databricks. The Azure data storage gets updated with new data on a daily basis.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif" size="3"&gt;What would be the best approach considering catalogs, schemas, external volumes, tables and so on?&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif" size="3"&gt;Thanks in advance.&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 08 Feb 2025 11:53:04 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/unity-catalog-for-medallion-architecture/m-p/109477#M43328</guid>
      <dc:creator>mbravonxp</dc:creator>
      <dc:date>2025-02-08T11:53:04Z</dc:date>
    </item>
    <item>
      <title>Re: Unity Catalog for medallion architecture</title>
      <link>https://community.databricks.com/t5/data-engineering/unity-catalog-for-medallion-architecture/m-p/109514#M43334</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/148362"&gt;@mbravonxp&lt;/a&gt;,&lt;/P&gt;
&lt;P class="p1"&gt;Create a separate catalog for each client to logically isolate their data. This helps in managing permissions and organizing data efficiently.&lt;/P&gt;
&lt;P class="p1"&gt;Within each catalog, create schemas for each environment (dev, pre, pro). This will help in managing the data lifecycle and access control for different stages of development&lt;/P&gt;
&lt;UL class="ul1"&gt;
&lt;LI class="li1"&gt;Implement the medallion architecture by creating separate schemas or tables within each environment for the bronze, silver, and gold layers. This will help in organizing the data processing pipeline and maintaining data quality.&lt;/LI&gt;
&lt;UL class="ul1"&gt;
&lt;LI class="li1"&gt;&lt;STRONG&gt;Bronze&lt;/STRONG&gt;: Raw data ingestion.&lt;/LI&gt;
&lt;LI class="li1"&gt;&lt;STRONG&gt;Silver&lt;/STRONG&gt;: Cleaned and enriched data.&lt;/LI&gt;
&lt;LI class="li1"&gt;&lt;STRONG&gt;Gold&lt;/STRONG&gt;: Aggregated and business-level data.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/UL&gt;
&lt;P class="p2"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="p1"&gt;Use Databricks jobs or workflows to automate the data processing and updating of tables in the bronze, silver, and gold layers&lt;/P&gt;
&lt;P class="p2"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="p1"&gt;&lt;STRONG&gt;Best Practices&lt;/STRONG&gt;:&lt;/P&gt;
&lt;UL class="ul1"&gt;
&lt;LI class="li1"&gt;Avoid giving direct storage-level access to users for Unity Catalog managed tables or volumes to maintain data security and governance.&lt;/LI&gt;
&lt;LI class="li1"&gt;Co-locate your Databricks workspace, metastore, and storage in the same Azure region for optimal performance&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Sat, 08 Feb 2025 22:25:42 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/unity-catalog-for-medallion-architecture/m-p/109514#M43334</guid>
      <dc:creator>Alberto_Umana</dc:creator>
      <dc:date>2025-02-08T22:25:42Z</dc:date>
    </item>
    <item>
      <title>Re: Unity Catalog for medallion architecture</title>
      <link>https://community.databricks.com/t5/data-engineering/unity-catalog-for-medallion-architecture/m-p/109726#M43373</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/148362"&gt;@mbravonxp&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;in this case the best approach is to have a single catalog per client per environment (so 9 catalogs in total).&lt;BR /&gt;In every catalog you will create bronze, silver and gold schema.&lt;BR /&gt;Additionally every catalog will have a separate storage and also, you may consider to have a separate workspace for each client for each environment.&lt;/P&gt;
&lt;P&gt;Check my answer to the similar topic on the forum:&lt;BR /&gt;&lt;A href="https://community.databricks.com/t5/community-platform-discussions/unity-catalog-implementation/td-p/84082" target="_blank" rel="noopener"&gt;https://community.databricks.com/t5/community-platform-discussions/unity-catalog-implementation/td-p/84082&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Feb 2025 07:42:12 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/unity-catalog-for-medallion-architecture/m-p/109726#M43373</guid>
      <dc:creator>filipniziol</dc:creator>
      <dc:date>2025-02-11T07:42:12Z</dc:date>
    </item>
    <item>
      <title>Re: Unity Catalog for medallion architecture</title>
      <link>https://community.databricks.com/t5/data-engineering/unity-catalog-for-medallion-architecture/m-p/109940#M43441</link>
      <description>&lt;P&gt;Hi both,&lt;/P&gt;&lt;P&gt;Thanks very much for the useful replies. Definitely I will go for your suggestions.&lt;/P&gt;&lt;P&gt;Best.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2025 08:25:56 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/unity-catalog-for-medallion-architecture/m-p/109940#M43441</guid>
      <dc:creator>mbravonxp</dc:creator>
      <dc:date>2025-02-12T08:25:56Z</dc:date>
    </item>
  </channel>
</rss>

