Azure Blob Storage Development

Azure Blob Storage is Microsoft's object storage solution for the cloud. It is optimized for storing massive amounts of unstructured data, such as text or binary data. Blob storage is ideal for serving images or documents directly to a browser, storing files for distributed access, streaming video and audio, storing data for backup and restore, disaster recovery, and archiving, and storing data for analysis by an on-premises or Azure-hosted service.

Blob storage consists of three components: a storage account, containers, and blobs. A storage account provides a unique namespace for your data. Every object in Azure Storage has a URL address that includes the storage account name. For example, https://mystorageaccount.blob.core.windows.net. Containers are similar to directories in a file system, organizing a set of blobs. A container can contain any number of blobs, and a storage account can contain any number of containers, up to 500 TB total capacity. Blobs are the actual data objects. There are three types of blobs: Block blobs (for text and binary data, up to ~4.75 TB), Append blobs (optimized for append operations, like logging), and Page blobs (for random read/write operations, up to 8 TB, used for VHDs).

When you upload a blob, Azure Storage splits the data into blocks (for block blobs) or pages (for page blobs). Each block is identified by a block ID. The client sends the blocks individually or in parallel. After all blocks are uploaded, the client commits the blob by sending a list of block IDs in order. Azure Storage then assembles the blob from these blocks. For read operations, the client requests the blob by its URL, and Azure Storage returns the entire blob or a range of bytes. Blob storage uses a flat namespace, but you can simulate a hierarchical structure by using a naming convention with forward slashes (e.g., container/folder1/subfolder2/blob.txt).

Using Azure CLI:

# Create a storage account
az storage account create --name mystorageaccount --resource-group myResourceGroup --location eastus --sku Standard_LRS --kind StorageV2

# Create a container
az storage container create --name mycontainer --account-name mystorageaccount --auth-mode login

# Upload a blob
az storage blob upload --container-name mycontainer --file myfile.txt --name myblob.txt --account-name mystorageaccount --auth-mode login

# List blobs
az storage blob list --container-name mycontainer --account-name mystorageaccount --auth-mode login --query "[].{name:name}"

# Set blob tier
az storage blob set-tier --container-name mycontainer --name myblob.txt --tier Cool --account-name mystorageaccount --auth-mode login

Using Azure PowerShell:

# Create a storage account
New-AzStorageAccount -ResourceGroupName myResourceGroup -Name mystorageaccount -Location eastus -SkuName Standard_LRS -Kind StorageV2

# Create a container
New-AzStorageContainer -Name mycontainer -Context (Get-AzStorageAccount -ResourceGroupName myResourceGroup -Name mystorageaccount).Context

# Upload a blob
Set-AzStorageBlobContent -Container mycontainer -File myfile.txt -Blob myblob.txt -Context (Get-AzStorageAccount -ResourceGroupName myResourceGroup -Name mystorageaccount).Context

# List blobs
Get-AzStorageBlob -Container mycontainer -Context (Get-AzStorageAccount -ResourceGroupName myResourceGroup -Name mystorageaccount).Context

You can define rules to automatically move blobs to a cooler tier or delete them after a specified number of days. For example:

{
  "rules": [
    {
      "enabled": true,
      "name": "moveToCool",
      "type": "Lifecycle",
      "definition": {
        "actions": {
          "baseBlob": {
            "tierToCool": { "daysAfterModificationGreaterThan": 30 },
            "tierToArchive": { "daysAfterModificationGreaterThan": 90 },
            "delete": { "daysAfterModificationGreaterThan": 2555 }
          }
        },
        "filters": {
          "blobTypes": ["blockBlob"],
          "prefixMatch": ["logs/"]
        }
      }
    }
  ]
}

Pricing is based on storage capacity (GB/month), data access operations (read/write/list), data transfer (egress), and data retrieval (for Cool and Archive tiers). Archive tier has the lowest storage cost but high retrieval cost and latency.

Upload a blob using .NET SDK:

string connectionString = "DefaultEndpointsProtocol=https;AccountName=mystorageaccount;AccountKey=...;EndpointSuffix=core.windows.net";
BlobServiceClient blobServiceClient = new BlobServiceClient(connectionString);
BlobContainerClient containerClient = blobServiceClient.GetBlobContainerClient("mycontainer");
BlobClient blobClient = containerClient.GetBlobClient("myblob.txt");
using FileStream uploadFileStream = File.OpenRead(@"C:\data\myfile.txt");
await blobClient.UploadAsync(uploadFileStream, true);
uploadFileStream.Close();

Generate a SAS token for a blob:

BlobClient blobClient = new BlobClient(connectionString, "mycontainer", "myblob.txt");
BlobSasBuilder sasBuilder = new BlobSasBuilder()
{
    BlobContainerName = "mycontainer",
    BlobName = "myblob.txt",
    Resource = "b", // b for blob, c for container
    ExpiresOn = DateTimeOffset.UtcNow.AddHours(1)
};
sasBuilder.SetPermissions(BlobSasPermissions.Read);
string sasToken = sasBuilder.ToSasQueryParameters(new StorageSharedKeyCredential("mystorageaccount", accountKey)).ToString();
Uri blobUriWithSas = new Uri($"{blobClient.Uri}?{sasToken}");

Azure Blob Storage is a scalable, secure, and cost-effective object storage solution. Understanding its architecture, access tiers, security features, and performance optimization is crucial for the AZ-204 exam. Practice using the Azure CLI, SDKs, and management tools to solidify your knowledge.

A video streaming service stores raw videos and processed MP4 files in Azure Blob Storage. They use Premium Block Blob Storage for low-latency access to popular content. They have a lifecycle policy that moves older content to Cool tier after 30 days and Archive after 90 days. They use Azure CDN to cache blobs at edge locations, reducing load on storage and improving user experience. They generate SAS tokens for temporary access to paid content. Misconfiguration: If they set the container public access level to 'container', anyone could list all blobs, leading to data exposure. They use Azure AD authentication for internal tools to avoid account key exposure.

An enterprise uses Azure Blob Storage for backup of on-premises databases. They use RA-GRS replication to ensure data is available in a secondary region in case of a disaster. They enable soft delete with a retention period of 14 days to protect against accidental deletion. They use immutable storage with time-based retention for compliance. They use AzCopy for bulk transfers. Common issue: If the retention policy is not set correctly, data may be deleted prematurely. They monitor blob capacity and transaction metrics with Azure Monitor alerts.

A data analytics company uses Azure Data Lake Storage Gen2 (built on Blob Storage) for its data lake. They enable hierarchical namespace for efficient directory operations. They use ACLs for fine-grained access control. They store petabytes of data in Parquet format. They use lifecycle management to move cold data to Cool tier. Performance considerations: They use multiple concurrent connections to maximize throughput. Misconfiguration: If they forget to enable hierarchical namespace at account creation, they cannot use POSIX-like permissions. They must recreate the account to enable it.