Azure Storage accounts: account types and storage services (Blob, Files, Queue, Table)
Slide deck explaining Azure Storage accounts, account types, and storage services: Blob Storage, Azure Files, Queue Storage, and Table Storage, including selection guidance and account configuration.
Azure Storage accounts: account types and storage services (Blob, Files, Queue, Table)
Introduction to Azure Storage accounts, account types, and storage services: Blob, Files, Queue, and Table.
Azure Storage accounts: account types and storage services (Blob, Files, Queue, Table)
Introduction to Azure Storage accounts, account types, and storage services: Blob, Files, Queue, and Table.
Azure Storage in one map
Start with a storage account, then pick the right storage service and account settings. Storage account equals starting point plus boundary. Services inside: Blob, Files, Queue, Table. Decision 1: service choice (what/how you store). Decision 2: account config (how it behaves).
Storage account: what you get
A storage account provides namespace plus endpoints plus a management/billing boundary. Top-level container for Azure Storage services. Unique namespace (account name). Service endpoints (URLs) over HTTP/HTTPS. Account-level settings plus billing boundary.
Pick the service by data + access
Choose Blob/Files/Queue/Table based on what you store and how you access it. Blob: objects over HTTP/HTTPS. Files: mountable file shares. Queue: messages for async work. Table: simple NoSQL key/attribute data.
Azure Blob Storage
Use Blob Storage when you want object access over HTTP/HTTPS. Best for unstructured data (images, video, backups). Organized as containers plus blobs. Accessed via URLs over HTTP/HTTPS. Not a mounted network drive.
Azure Files
Use Azure Files when you need mountable SMB/NFS file shares. Managed file shares in Azure. Mount via SMB (Windows-style) or NFS (Unix/Linux-style). Fits 'shared folder / network drive' needs. Different from Blob object storage.
Azure Queue Storage
Use Queue Storage to decouple components with asynchronous work items. Message queue for work items. Frontend posts message → worker processes later. Helps with async processing and decoupling. Not the same as storing records.
Azure Table Storage
Use Table Storage for simple, schemaless NoSQL key/attribute data. Stores entities with properties (schemaless). Lightweight structured data. No relational joins. Good for simple records, not complex relationships.
Storage account types (the key idea)
Account type affects features and performance; Standard GPv2 is the common default. Standard GPv2 (General-purpose v2) equals common default. Supports typical service mix (Blob/Files/Queue/Table). Specialized types exist for specific workloads. Type can enable/limit features.
Two-bucket decision rule
Choose the service first, then choose account-level settings like redundancy and networking. Service choice: Blob vs Files vs Queue vs Table. Account config: redundancy, performance, networking, security. Redundancy examples: LRS / ZRS / GRS. Don't mix 'what' with 'how it behaves'.
Clue → service cheat sheet
Listen for access style clues, then pick the matching service. URL access (HTTP/HTTPS) → Blob Storage. Mount a drive (SMB/NFS) → Azure Files. Work backlog → Queue Storage. Simple NoSQL records → Table Storage.
Plan ahead: not every change is in-place
Some upgrades exist, but many type changes require a new account and migration. Some account upgrades are supported (e.g., to GPv2). Not every type change is an in-place switch. Often requires: new account → migrate data → cut over. Avoid 'we'll fix it later' assumptions.