Azure Table Storage vs CosmosDB Table API
Azure Table Storage vs CosmosDB Table API
Azure Table Storage vs CosmosDB Table API
Re: Azure Table Storage vs CosmosDB Table API
As Peter responded, DocumentDB now is part of [Cosmos DB](https://learn.microsoft.com/en-us/azure/cosmos-db/introduction), it is one of the [many Data Models](https://learn.microsoft.com/en-us/azure/cosmos-db/introduction#data-models) the new service has available including [MongoDB API](https://learn.microsoft.com/en-us/azure/documentdb/documentdb-protocol-mongodb), [Premium Tables API](https://learn.microsoft.com/en-us/azure/cosmos-db/table-introduction), and [Gremlin Graph API](https://learn.microsoft.com/en-us/azure/cosmos-db/graph-introduction).
They all have the same [global distribution](https://learn.microsoft.com/en-us/azure/cosmos-db/introduction#global-distribution) capabilities and [consistency levels](https://learn.microsoft.com/en-us/azure/documentdb/documentdb-consistency-levels).
Now, going to your Tables question, both services have a different scenario and pricing model.
While Azure Storage Tables is aimed at high capacity on a single region (optional secondary read only region but no failover), indexing by PK/RK and storage-optimized pricing; Azure Cosmos DB Tables aims for high throughput (single-digit millisecond latency), global distribution (multiple failover), SLA-backed predictive performance with automatic indexing of each attribute/property and a pricing model focused on throughput.
Depending on your scenario is the service you might want to use, Azure Storage Tables is still a great solution, but if, for example, you need global distribution, Cosmos DB Tables is a best suited service.
They all have the same [global distribution](https://learn.microsoft.com/en-us/azure/cosmos-db/introduction#global-distribution) capabilities and [consistency levels](https://learn.microsoft.com/en-us/azure/documentdb/documentdb-consistency-levels).
Now, going to your Tables question, both services have a different scenario and pricing model.
While Azure Storage Tables is aimed at high capacity on a single region (optional secondary read only region but no failover), indexing by PK/RK and storage-optimized pricing; Azure Cosmos DB Tables aims for high throughput (single-digit millisecond latency), global distribution (multiple failover), SLA-backed predictive performance with automatic indexing of each attribute/property and a pricing model focused on throughput.
Depending on your scenario is the service you might want to use, Azure Storage Tables is still a great solution, but if, for example, you need global distribution, Cosmos DB Tables is a best suited service.