Cyberiafreak

"Fortunate are those who take the first steps.” ― Paulo Coelho

Windows Azure storage getting started

My reading notes from this book which I bought recently – Developing Cloud Applications with Windows Azure Storage by Paul Mehner.

th

I will try simplify the content with examples for quicker references. Hope you enjoy this series about Windows Azure Storage.

+ Windows Azure Storage(WAS) – provides independent data management services to our application – data storage for any application/any platform/any language over HTTP

+  We are moving to NoSQL era due to volume of data/performance. In 1970’s we started with flat file –> file based relational db’s -> Relational -> Hierarchical -> N/w -> Federated -> NoSQL (not only SQL).

+ WAS is implements as NoSQL-styled db.

+ There are 3 high level data types in WAS – Blob, Tables and Queues.

+ WAS is not a relational db

+ Access to this WAS is done with simple REST API

+ WAS supports scalability, replication, geo-locaiton, geo-replication, independent and interoperability, maintains fully consistent model (Amazon S3 is eventually consitent model – read operation after update may/may not return the very recent updated data)

BLOBS (for storing unstructured data –  doc, pictures, videos and music)

=======

>  Windows Azure blob service provides a simple RESTful APi for storing and retrieving unstructured data.

> Blobs are organized into Containers(similar to directories), you can have any number of blob’s under containers.

> Blobs and blob containers are easily accessible with unique url’s.

> You can set public access as well.

> Ideal for the storage of web content

Tables

=====

> Windows Azure Table service  provides a simple RESTful Api for storing massive amounts of semi structured data.

> These tables are not at all like relational db tables.

> Rows are called entities, consist of properties, which are like columns.

> Different rows stored in the same table can often have different set of properties.

Queue

=====

> Queues do not provide permanent storage of the message they handle.

> Unprocessed messages will be deleted from the queue after 7 days.

> Same like MSMQ, it will get deleted upon read, exposed through RESTful API’s.

Happy Azuring!

Advertisements

February 2, 2015 - Posted by | Azure Storage |

No comments yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: