Windows azure table storage – deep dive

Windows Azure Table Storage – Deep Dive Sundararajan Subramanian Associate Technical Architect

Azure - Storage Tables – Provide structured storage. A Table is a set of entities, which contain a set of properties Queues – Provide reliable storage and delivery of messages for an application Blobs – Provide a simple interface for storing named files along with metadata for the file Drives – Provides durable NTFS volumes for Windows Azure applications to use 2

Windows Azure Tables Provides Structured Storage Massively Scalable Tables Billions of entities (rows) and TBs of data Can use thousands of servers as traffic grows Highly Available & Durable Data is replicated several times Familiar and Easy to use API ADO.NET Data Services – .NET 3.5 SP1 .NET classes and LINQ REST – with any platform or language 3

Table Storage Concepts Entities Tables Accounts Blogtitle=… Name = … BlogPosts Blogtitle=… Name = … sundars Name=… Id= … Users Name=… Id= … 4

Table Data Model Table A storage account can create many tables Table name is scoped by account Set of entities (i.e. rows) Entity Set of properties (columns) Required properties PartitionKey, RowKey and Timestamp 5

Required Entity Properties PartitionKey & RowKey Uniquely identifies an entity Defines the sort order Use them to scale your application Timestamp Read only Optimistic Concurrency 6

PartitionKey And Partitions PartitionKey Used to group entities in the table into partitions A table partition All entities with same partition key value Unit of scale Control entity locality Row key provides uniqueness within a partition 7

Partitioning Tables Partition 1 Partition 2

Partitioning – Why? ,[object Object],Each individual partitions are distributed across multiple storage nodes System monitors the Partition usage and automatically balances partitions across multiple storage nodes. Apartition i.e. all entities with same partition key, will be served by a single node ,[object Object],Allows the application to atomically perform multiple Create/Update/Delete operations across multiple entities in a single batch request to the storage system ,[object Object],[object Object]

Demo Blog Engine – Windows Azure Table Storage

DataService Context – Best Practices ,[object Object]

Use separate Dataservice Context object for each operationIf dataservice context object is shared across multiple operations the error cause in one of the operation will be retried during the subsequent SaveChanges. ,[object Object],[object Object]

When an update happens to the retrieved entity, the client sends the Etag back to the server.

Server checks for the Etag of the persisted entity before update.

If there is a mismatch, server throws an exception,[object Object],[object Object]

Continuation tokens ,[object Object]

At the end of partition range boundary

Maximum of 5 seconds to execute the query

Expect Continuation token alwaysIf the Query times out, Server returns a continuation token so that the client can make another query When the Scan crosses partition boundary, continuation tokens are returned

Windows azure table storage – deep dive

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (9)

Similar to Windows azure table storage – deep dive

Similar to Windows azure table storage – deep dive (20)

Recently uploaded

Recently uploaded (20)

Windows azure table storage – deep dive