Skip to main content

Choosing the Right Azure Storage Account: A Comprehensive Guide

What are the different types of Azure Storage accounts and their key differences?


Azure offers several types of storage accounts, each tailored for different scenarios. Here are the main types:

  1. General-purpose v2 (GPv2): Supports all Azure Storage services (Blobs, Files, Queues, and Tables). It’s the most versatile and recommended for most scenarios.
  2. Blob Storage: Optimized for storing unstructured data like text and binary data. It supports hot, cool, and archive access tiers.
  3. General-purpose v1 (GPv1): An older version of GPv2, supporting Blobs, Files, Queues, and Tables but with fewer features and higher costs for some operations.
  4. Block Blob Storage: Premium storage for block blobs and append blobs, offering low latency and high throughput.
  5. FileStorage: Premium storage for Azure Files, providing high performance for file shares.

When to Use Each Type

  • GPv2: Use for most scenarios, including applications that require a mix of different storage services.
  • Blob Storage: Ideal for scenarios where you need to store large amounts of unstructured data and want to optimize costs with different access tiers.
  • GPv1: Suitable for legacy applications that were designed for this type.
  • Block Blob Storage: Best for workloads with high transaction rates or requiring low latency.
  • FileStorage: Use for enterprise or high-performance applications needing file shares.

Key Differences

  1. Supported Services:
    • GPv2: Supports Blobs, Files, Queues, and Tables.
    • Blob Storage: Only supports Blob storage.
    • GPv1: Supports Blobs, Files, Queues, and Tables but with fewer features.
    • Block Blob Storage: Only supports Block and Append Blobs.
    • FileStorage: Only supports Azure Files.
  2. Performance:
    • GPv2 and GPv1: Standard performance.
    • Block Blob Storage and FileStorage: Premium performance with SSDs.
  3. Access Tiers:
    • GPv2 and Blob Storage: Support hot, cool, and archive tiers.
    • GPv1, Block Blob Storage, and FileStorage: Do not support access tiers.
  4. Redundancy Options:
    • GPv2: Offers LRS, GRS, RA-GRS, ZRS, GZRS, and RA-GZRS.
    • Blob Storage: Offers LRS, GRS, RA-GRS, ZRS.
    • GPv1: Offers LRS, GRS, RA-GRS.
    • Block Blob Storage and FileStorage: Offer LRS and ZRS.
  5. Pricing:
    • GPv2: Generally more cost-effective for most scenarios.
    • Blob Storage: Cost-effective for large amounts of unstructured data with tiered pricing.
    • GPv1: Higher costs for some operations compared to GPv2.
    • Block Blob Storage and FileStorage: Higher costs due to premium performance.

These differences help you choose the right storage account based on your specific needs123.

 

Labels:

Comments

Post a Comment

Popular posts from this blog

Azure key vault with .net framework 4.8

Azure Key Vault  With .Net Framework 4.8 I was asked to migrate asp.net MVC 5 web application to Azure and I were looking for the key vault integrations and access all the secrete out from there. Azure Key Vault Config Builder Configuration builders for ASP.NET  are new in .NET Framework >=4.7.1 and .NET Core >=2.0 and allow for pulling settings from one or many sources. Config builders support a number of different sources like user secrets, environment variables and Azure Key Vault and also you can create your own config builder, to pull in configuration from your own configuration management system. Here I am going to demo Key Vault integrations with Asp.net MVC(download .net framework 4.8). You will find that it's magical, without code, changes how your app can read secretes from the key vault. Just you have to do the few configurations in your web config file. Prerequisite: Following resource are required to run/complete this demo · ...
Post a Comment
Read more

How to Make a Custom URL Shortener Using C# and .Net Core 3.1

C# and .Net Core 3.1:  Make a Custom URL Shortener Since a Random URL needs to be random and the intent is to generate short URLs that do not span more than 7 - 15 characters, the real thing is to make these short URLs random in real life too and not just a string that is used in the URLs Here is a simple clean approach to develop custom solutions Prerequisite:  Following are used in the demo.  VS CODE/VISUAL STUDIO 2019 or any Create one .Net Core Console Applications Install-Package Microsoft.AspNetCore -Version 2.2.0 Add a class file named ShortLink.cs and put this code: here we are creating two extension methods. public   static   class   ShortLink {      public   static   string   GetUrlChunk ( this   long   key ) =>            WebEncoders . Base64UrlEncode ( BitConverter . GetBytes ( key ));      public   static   long   GetK...
Post a Comment
Read more

Azure Logic Apps Send Email Using Send Grid Step by Step Example

Azure Logic Apps Send Email Using Send Grid Step by Step     Step 1- Create Send Grid Account Create a SendGrid Account  https://sendgrid.com/ Login and Generate Sendgrid Key and keep it safe that will be used further to send emails You can use Free service. it's enough for the demo purpose Step 2- Logic App Design Login to  https://portal.azure.com Go to Resources and Create Logic App Named "EmailDemo" Go To Newly Created Rosoure Named "EmailDemo" and Select a Trigger "Recurrence", You can choose according to your needs like HTTP, etc. Note* Without trigger you can not insert new steps or Actions Click on Change Connection and add Send Grid Key  Click on Create and Save Button on the Top. As we have recurrence so it will trigger according to our setup(every 3 months) so just for the test click on "RUN" button  Finally, you should get an email like below one:
Post a Comment
Read more