<?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: Appropriate storage account type for reference data (Azure) in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/appropriate-storage-account-type-for-reference-data-azure/m-p/41503#M27365</link>
    <description>&lt;P&gt;+1 for ADLS.&amp;nbsp; Hierarchical storage, hot/cold/premium storage, things not possible in blob storage&lt;/P&gt;</description>
    <pubDate>Fri, 25 Aug 2023 11:49:37 GMT</pubDate>
    <dc:creator>-werners-</dc:creator>
    <dc:date>2023-08-25T11:49:37Z</dc:date>
    <item>
      <title>Appropriate storage account type for reference data (Azure)</title>
      <link>https://community.databricks.com/t5/data-engineering/appropriate-storage-account-type-for-reference-data-azure/m-p/41350#M27336</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We are using a reference dataset for our Production applications. We would like to create a delta table for this dataset to be used from our applications. Currently, manual updates will occur on this dataset through a script on a weekly basis. On the future, we will create a streaming job from Event Hub to propagate changes in real time through streaming jobs (Spark Streaming or DLT Pipelines). The expected rate of updates is 1000 to 10000 insertions/updates per hour.&lt;/P&gt;&lt;P&gt;Currently, we have an Azure blob storage account that contains all production reference data that is mounted on the corresponding databricks instance. The question is whether we should create an ADLS storage account for this Delta Table or the Blob storage account can handle this architecture. Are there any future plans to drop compatibility between blob storage and Delta?&lt;/P&gt;&lt;P&gt;Kind regards.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Aug 2023 14:12:24 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/appropriate-storage-account-type-for-reference-data-azure/m-p/41350#M27336</guid>
      <dc:creator>EDDatabricks</dc:creator>
      <dc:date>2023-08-24T14:12:24Z</dc:date>
    </item>
    <item>
      <title>Re: Appropriate storage account type for reference data (Azure)</title>
      <link>https://community.databricks.com/t5/data-engineering/appropriate-storage-account-type-for-reference-data-azure/m-p/41385#M27348</link>
      <description>&lt;P&gt;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/63237"&gt;@EDDatabricks&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In my experience, I have mostly seen users choose ADLS for a similar use case. So, I believe ADLS is a more popular choice.&lt;/P&gt;&lt;P&gt;I have not seen many users go for blob storage but I am hoping someone who has explored blob storage more could add to my comment.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Aug 2023 18:18:22 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/appropriate-storage-account-type-for-reference-data-azure/m-p/41385#M27348</guid>
      <dc:creator>Lakshay</dc:creator>
      <dc:date>2023-08-24T18:18:22Z</dc:date>
    </item>
    <item>
      <title>Re: Appropriate storage account type for reference data (Azure)</title>
      <link>https://community.databricks.com/t5/data-engineering/appropriate-storage-account-type-for-reference-data-azure/m-p/41503#M27365</link>
      <description>&lt;P&gt;+1 for ADLS.&amp;nbsp; Hierarchical storage, hot/cold/premium storage, things not possible in blob storage&lt;/P&gt;</description>
      <pubDate>Fri, 25 Aug 2023 11:49:37 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/appropriate-storage-account-type-for-reference-data-azure/m-p/41503#M27365</guid>
      <dc:creator>-werners-</dc:creator>
      <dc:date>2023-08-25T11:49:37Z</dc:date>
    </item>
  </channel>
</rss>

