Azure Storage Services

# CHAPTER 5

Azure Storage Services #

1. Introduction #

2. Learning Objectives #

• Define the four core services: Blob, File, Queue, and Table storage.

• Understand the hierarchy of Storage Accounts and Containers.

• Choose the correct Access Tier (Hot, Cool, Cold, Archive).

• Upload and manage blobs via the Azure Portal.

• Host a public, static HTML website using Azure Blob Storage.

3. Beginner-Friendly Explanation #

• Disk Storage (VM Hard Drives): Like a filing cabinet in your office. Fast, structured, but has a strict physical limit. When it's full, you have to buy a bigger cabinet.

• Blob Storage (Azure Storage): Like throwing boxes into an infinitely expanding warehouse. You don't organize the boxes on shelves; you just attach a barcode label (the URL) to the box and throw it in. When you need the box, you ask the warehouse for the barcode, and it instantly retrieves it. The warehouse never gets full, and you only pay for the exact space your boxes take up.

4. The Four Core Storage Services #

1. 1. Blob Storage: "Binary Large Object". Designed for massive amounts of unstructured data (Images, Videos, Backups, Documents). This is the most popular service.

1. 2. File Storage: Fully managed file shares accessible via standard SMB protocol. You can mount it like a network Z: drive on multiple Windows VMs simultaneously.

1. 3. Queue Storage: A messaging store for reliable communication between application components (used to decouple microservices).

1. 4. Table Storage: A NoSQL key/attribute store for rapid development using massive datasets.

5. Access Tiers (Saving Money) #

1. 1. Hot Tier: Best for data accessed frequently (e.g., profile pictures on a live website). Highest storage costs, lowest access costs.

1. 2. Cool Tier: Best for data stored for at least 30 days and accessed infrequently (e.g., short-term backups).

1. 3. Cold Tier: Best for data stored for at least 90 days.

1. 4. Archive Tier: Best for data you hope to *never* access, stored for at least 180 days (e.g., legal compliance logs). Extremely cheap to store, but incredibly expensive and slow (can take up to 15 hours) to download!

6. Storage Accounts and Containers #

• Storage Account: The top-level namespace. *Crucial Rule:* Storage Account names must be Globally Unique across all of Azure, all lowercase, with no spaces (e.g., myphotostore12345).

• Container: A folder inside the Storage Account.

• Blob: The actual file (e.g., image.jpg) inside the Container.

7. Mini Project: Host a Static Website #

Step-by-Step Tutorial:

1. 1. On your laptop, create an index.html file with a simple <h1>Hello World from Azure Storage!</h1> tag.

1. 2. In the Azure Portal, search for Storage accounts. Click + Create.

1. 3. Resource group: rg-web-demo.

1. 4. Storage account name: Give it a unique, lowercase name (e.g., myazurewebsite9988).

1. 5. Region: East US.

1. 6. Redundancy: Choose Locally-redundant storage (LRS) to save money. Click Review + create, then Create.

1. 7. Once deployed, go to the resource.

1. 8. Scroll down the left menu to Data management and click Static website.

1. 9. Click Enabled.

1. 10. Index document name: type index.html. Click Save.

1. 11. Azure automatically creates a special container named $web and provides you a Primary endpoint URL. Copy this URL.

1. 12. Now, go to the left menu under Data storage and click Containers.

1. 13. Click the $web container.

1. 14. Click Upload, and select your index.html file from your laptop.

1. 15. Paste the Primary endpoint URL into your browser. Your website is live on the internet, and you are paying fractions of a penny to host it!

8. Real-World Scenarios #

9. Best Practices #

• Shared Access Signatures (SAS): Never share your Storage Account Access Keys! If you want to let a user temporarily download a private file, generate a SAS URL. It is a unique link that grants read-only access to a specific file, and automatically expires after exactly 10 minutes.

10. Cost Optimization Tips #

• Use the Right Tier: If you dump 50 Terabytes of disaster recovery backups into the "Hot" tier, you will receive a massive bill. Analyze how often data is accessed and relentlessly utilize Cool or Archive tiers for backups.

11. CLI Examples #

az storage container create \
    --name my-images \
    --account-name myazurewebsite9988 \
    --auth-mode login

12. Exercises #

1. 1. Why must an Azure Storage Account name be globally unique across all of Azure?

1. 2. Explain the financial tradeoff between the Hot access tier and the Archive access tier.

13. FAQs #

14. Interview Questions #

• Q: Describe the architectural difference between Disk Storage (Managed Disks) and Object Storage (Blob). When would you architecturally mandate the use of one over the other?

• Q: A client needs to store petabytes of financial compliance logs that must be retained for 5 years but will likely never be audited. Detail your storage tier recommendation and explain how you would automate the cost-reduction pipeline over time.

15. Summary #

16. Next Chapter Recommendation #