Raw media upload
Cloud / Knowledge library
Azure Blob Storage
Stores massive amounts of object data in containers with access tiers and lifecycle policies
Why learn Azure Blob Storage?
Teams use Azure Blob Storage to adopt object storage without building the complete underlying platform themselves.
The problem it solves
Stores durable unstructured objects addressed by keys inside logical containers
Where it came from
Azure Blob Storage is Microsoft Azure's offering for object storage. Its closest catalog counterparts are Amazon S3 and Google Cloud Storage; they address the same broad need but are not feature-for-feature identical.
Build your understanding
Work through these exercises in order. Try the task before opening a reference.
- Explain the main responsibility of Azure Blob Storage.
- Choose a workload that fits Azure Blob Storage.
- Identify one operational tradeoff of Azure Blob Storage.
- Compare Azure Blob Storage with Amazon S3.
- Compare Azure Blob Storage with Google Cloud Storage.
Documentation and sources
- Microsoft Azure product catalog (azure.microsoft.com)
Connect the ideas
Alternatives
Real World Example
Media Archive Lifecycle Management
Digital media production companies managing massive libraries of raw video assets.
The business problem
High storage costs due to keeping infrequently accessed historical footage in high-performance storage tiers.
How this topic solves it
Azure Blob Storage allows for the organization of massive amounts of object data into containers, utilizing access tiers to move older content to cooler storage and lifecycle policies to automate this transition.
- Create a storage account and define containers for raw and processed media assets.
- Upload video files into the Hot access tier for immediate post-production access.
- Configure a lifecycle management policy to transition blobs to the Archive tier after 90 days of inactivity.
- Apply rules to permanently delete blobs older than seven years to maintain compliance and storage efficiency.
Visualizes the movement of media assets through storage tiers based on age.
Active production assets
Historical footage
End of lifecycle
- Ingestion → Initial upload → Hot Tier
- Hot Tier → Lifecycle policy (90 days) → Archive Tier
- Archive Tier → Lifecycle policy (7 years) → Deletion
Expected business outcome
Reduced operational storage overhead by automatically transitioning aged assets to lower-cost tiers without manual intervention.
Limitations and checks
Data in the Archive tier is not immediately available for read operations; it requires a rehydration process that can take several hours to complete.