Azure Table Storage
activeby Microsoft · since 2010 · also known as Azure Tables, Azure Storage Tables
Cheap, schemaless key-attribute store inside an Azure Storage account.
Overview
Azure Table Storage is one of the original Azure Storage services: entities with up to 252 properties, addressed by a PartitionKey and RowKey, served over a REST/OData API from a general-purpose storage account. It is very inexpensive for large volumes of simple records and needs no provisioning, which keeps it popular for logs, device metadata and app configuration. The trade-off is that only the two keys are indexed, batch transactions are limited to one partition, and latency is not guaranteed. Teams that outgrow it usually move to Azure Cosmos DB for Table, which exposes the same API with global distribution and SLAs.
Strengths & trade-offs
Strengths
- +Very low cost per GB for large volumes of simple entities
- +Zero provisioning; lives in a storage account you probably already have
- +Same API as Azure Cosmos DB for Table, so there is an upgrade path
- +Strongly consistent reads within the primary region
Trade-offs
- −Only PartitionKey and RowKey are indexed; other filters scan
- −Entity group transactions limited to 100 entities in one partition
- −No latency SLA and throughput caps per partition and account
- −Feature set has barely changed in years
Great for
- +Application logs and diagnostics
- +Device and user metadata keyed by ID
- +Lightweight configuration storage
- +Cheap archival of structured records
Think twice for
- −Queries on non-key properties
- −Low-latency global applications
- −Complex transactions or relational data
Capabilities
Native or official first-party support · 4 of 25 tracked
Scale & consistency
- Comfortable data size
- Large · ≤ 1 PB
- Horizontal scaling
- Native
- Multi-region
- Read replicas
- Transactions
- Limited ACID
- Consistency
- Strong
- Schema
- Schemaless
- Architecture
- Distributed, Serverless
- Query languages
- OData
Partitions are spread automatically; storage accounts are capped by account-level throughput targets. RA-GRS gives a read-only secondary region.
Deployment
available on · Azure
Ecosystem
Alternatives to Azure Table Storage
Microsoft's globally distributed, multi-API NoSQL and vector database with SLA-backed latency.
azure-table-storage vs azure-cosmos-db →AWS's serverless key-value and document store with single-digit-millisecond reads at any scale.
azure-table-storage vs amazon-dynamodb →Google's managed wide-column store, the original Bigtable, with HBase API and SQL access.
azure-table-storage vs google-cloud-bigtable →Globally cached, eventually consistent key-value store for read-heavy data at Cloudflare's edge.
azure-table-storage vs cloudflare-workers-kv →Hadoop's Bigtable clone: strongly consistent wide-column tables on top of HDFS.
azure-table-storage vs apache-hbase →Serverless, CQL-compatible Cassandra service on AWS with no clusters to manage.
azure-table-storage vs amazon-keyspaces →Azure Table Storage FAQ
What is Azure Table Storage?
Azure Table Storage is a key-value database by Microsoft, first released in 2010. Azure Table Storage is one of the original Azure Storage services: entities with up to 252 properties, addressed by a PartitionKey and RowKey, served over a REST/OData API from a general-purpose storage account. It is very inexpensive for large volumes of simple records and needs no provisioning, which keeps it popular for logs, device metadata and app configuration. The trade-off is that only the two keys are indexed, batch transactions are limited to one partition, and latency is not guaranteed. Teams that outgrow it usually move to Azure Cosmos DB for Table, which exposes the same API with global distribution and SLAs.
Is Azure Table Storage open source?
No. Azure Table Storage is proprietary, closed-source software.
Does Azure Table Storage support ACID transactions?
Partly. Azure Table Storage offers limited ACID guarantees (for example, single-record or single-partition transactions), with strong consistency.
Does Azure Table Storage scale horizontally?
Azure Table Storage scales horizontally out of the box, with built-in sharding or partitioning. It is comfortable at large scale (≤ 1 PB). It supports cross-region read replicas.
How can I run Azure Table Storage?
You can use the vendor's managed cloud and run it serverless. It is available on Azure.
What is Azure Table Storage best for?
Azure Table Storage is a strong fit for application logs and diagnostics; device and user metadata keyed by ID; and lightweight configuration storage. Think twice for queries on non-key properties.
What are the best alternatives to Azure Table Storage?
Common alternatives to Azure Table Storage include Azure Cosmos DB, Amazon DynamoDB, Google Cloud Bigtable, Cloudflare Workers KV and Apache HBase. The right choice depends on your workload, scale and hosting; WhichDB's smart match ranks them against your requirements.
How popular is Azure Table Storage?
Azure Table Storage ranks #162 of 844 databases on the WhichDB Score (19.7/100), and #22 among key-value databases. The score combines public adoption signals such as package downloads, GitHub activity, job posts and developer discussion.