Azure Table Storage: Cloud NoSQL for Dummies | Microsoft azure for dummies

Posted on

What is Azure Table in Microsoft azure for dummies?

Storage of vast volumes of structured, non-relational data may be done in the cloud with Azure Table storage, a NoSQL datastore. The schemaless architecture of Azure Table allows you to store several entity types in a single table. A collection of properties specifies a name-value pair that is part of an entity. Users who are just getting their feet wet with NoSQL or cloud data services will find Azure Table to be a perfect starting point due to its lightweight and easily managed nature.

As part of the Azure file storage ecosystem, we will discuss the fundamentals of Azure Table and draw parallels between the traditional Azure Table service and the new Azure Cosmos DB Table API in this post. We’ll also demonstrate how Azure NetApp Files’ exceptional file throughput and sub-millisecond response times may facilitate the migration of additional apps to Azure, including mission-critical workloads.

You can store metadata and flexible datasets in Table storage. It lets you store as many entities as you want, and each storage account you use can hold as many tables as your storage space will allow. Azure Table storage is a database you can use to store NoSQL data in Azure. Using a key/attribute design, it lets you store structured data without a schema.

It can also be used for structured data that is not related to other data. Through the Azure Cosmos DB Table API, you can also use Azure Table storage. This is a paid service that gives you automatic secondary indexes, global distribution, and tables that are better for throughput.

Azure Table Storage vs Azure Cosmos DB Table API

Microsoft azure for dummies

Cosmos DB Table API and Azure Table storage can both do some of the same things, but they are not the same service. Read on to find out how these services are different and what they can do.


When you use Azure Table storage in Microsoft azure for dummies, your operations can take as long as they need to take. Cosmos DB, on the other hand, keeps read/write latency to less than 10 milliseconds. With Azure Table, you can only do up to 20,000 operations per second, but you can do up to 10 million operations per second with Cosmos DB. Property indexing is also done automatically by Cosmos DB. This can be used to speed up the querying process.

Global distribution

You can use Azure Table in one region and in a second, read-only region to make it more available. On the other hand, you can spread your data across up to 30 regions with Cosmos DB. Included is automatic failover on a global scale, and you can choose from five consistency levels to get the right mix of throughput, latency, and availability.

Consistent API

With both Azure Table and Cosmos DB, you can use the same API. For a generic REST API, there are also software development kits (SDKs) that can be used. But with Cosmos DB, there is a superset of features that you can use for more methods. Since the API is the same for both Azure Table and Cosmos DB, it is easy to move data between the two.


Table storage charges you based on how much storage you use. The price is per GB and depends on the level of redundancy you choose. The price goes down the more GB you use. You are also charged per 10k operations, which is a measure of how many operations you do.

Billing in Cosmos DB is based on how many throughput request units are used (RUs). Your database is set up in 100RU per second chunks, and you are charged by the hour for any units you use. You are also charged more per GB for storage than you are for Table storage.