Q64. What are the benefits of table storage?
- Table storage is highly available and massively scalable storage.
Highly available which means ALWAYS available, is possible because the data in a Table storage is replicated in 3 places within the same datacenter. And to ensure the stated goal of higher availability, the data is asynchronously replicated in a different data center of the same region.
Massively scalable storage means increase in table size to store small volume of data and if need arises store large volume of data. Massive scaling is possible because table storage maintains its data in partitions and each partition can be stored in many storage nodes depends on the data needs. - Microsoft has priced its charges for storage very competitively and at this point in time few competitors offer such pricing and this storage is also lower in cost than traditional SQL server for similar volumes of data.
- Today’s modern applications require scalable databases and so Table storage meets today’s application requirements.
- The storage limit of a storage account is 500 TB which is lot of data and any number entities (billions of entities) can be placed in a table with in this limit.
- Table storage does not enforce any schema, and this makes application design different from applications which work with traditional relational databases. As there is no schema in the table, any type of structured data can be added to the same table provided you use the partition key. I will explain about this in one of the upcoming questions.
- Table storage is easy to use and so developers can create table based applications quite easily. This is because it not required to design the database prior to creating an application. If an application requires to add additional data for a particular entity, we can do that. This is possible because Table storage does not insist on a fixed schema.
See More Questions and Answers on - Azure Table Storage
- Why should i use Azure table storage?
- Difference between sql database table and Azure storage table?
- Explain Azure table storage data model?
- why to partition Azure table?
- What is Azure table primary key?
- Guidelines on how to choose partition key and row key?
- Explain how partition key is linked to scalability?
- How do partitions work in storage services like blobs and queues?
- What are entity group transactions?