What is Azure Cosmos DB for Table?
APPLIES TO: Table
Azure Cosmos DB is a fully managed NoSQL and relational database for modern app development.
Azure Cosmos DB for Table provides applications written for Azure Table storage with premium capabilities like:
- Turnkey multiple-region distribution.
- Dedicated throughput around China (when using provisioned throughput).
- Single-digit millisecond latencies at the 99th percentile.
- Guaranteed high availability.
- Automatic secondary indexing.
Azure Table Storage has SDKs available for .NET, Java, Python, Node.js, and Go. These SDKs can be used to target either Azure Table Storage or the API for Table. Applications written for Azure Table Storage using the Azure Tables SDKs can be migrated to the Azure Cosmos DB with no code changes to take advantage of premium capabilities.
Specifically, the .NET Azure Tables SDK Azure.Data.Tables offers the latest features supported by the API for Table. The Azure Tables client library can seamlessly target either Azure Table storage or API for Table service endpoints with no code changes.
API for Table benefits
If you currently use Azure Table Storage, you gain the following benefits by moving to the API for Table:
|Azure Table storage||API for Table|
|Latency||Fast, but no upper bounds on latency.||Single-digit millisecond latency for reads and writes, backed with <10-ms latency for reads and writes at the 99th percentile, at any scale, anywhere in China.|
|Throughput||Variable throughput model. Tables have a scalability limit of 20,000 operations/s.||Highly scalable with dedicated reserved throughput per table backed by SLAs. Accounts have no upper limit on throughput and support >10 million operations/s per table.|
|Multiple-region distribution||Single region with one optional readable secondary read region for high availability.||Turnkey multiple-region distribution from one to any number of regions. Support for service-managed and manual failovers at any time, anywhere in China. Multiple write regions to let any region accept write operations.|
|Indexing||Only primary index on PartitionKey and RowKey. No secondary indexes.||Automatic and complete indexing on all properties by default, with no index management.|
|Query||Query execution uses index for primary key, and scans otherwise.||Queries can take advantage of automatic indexing on properties for fast query times.|
|Consistency||Strong within primary region. Eventual within secondary region.||Five well-defined consistency levels to trade off availability, latency, throughput, and consistency based on your application needs.|
|Pricing||Consumption-based.||Available in both consumption-based and provisioned capacity modes.|
|SLAs||99.9% to 99.99% availability, depending on the replication strategy.||99.999% read availability, 99.99% write availability on a single-region account and 99.999% write availability on multi-region accounts. Comprehensive SLAs covering availability, latency, throughput and consistency.|