Windows Azure Storage Overview

Posted By: Ryan Dunn | Jul 31st, 2009 @ 10:17 AM | 39,267 Views | 6 Comments
A key component of any cloud computing offering is durable storage.  Windows Azure provides 3 forms of durable storage: tables, blobs, and queues.  Join me as we explore the highlights of these 3 important implementations.

Related Videos

How Do I: Store Blobs in Windows Azure Storage?
How Do I: Leverage Queues in Windows Azure?
How Do I: Store Data in Windows Azure Tables?
How Do I: Use Paging in Windows Azure Tables?
How Do I: Leverage Concurrency in Windows Azure Tables?

Related Hands on Labs

Getting Started with Windows Azure Storage
Using Windows Azure Tables
Rating:
1
0
#Nov 25th, 2009 @ 6:41 PM
Shanester
Shanester
Autobot

Clicking the Full Screen button causes the video to crash.

 

I'm using Internet Explorer 8.

 

Shane.

#Dec 7th, 2009 @ 2:43 AM
jigneshpandya
jigneshpandya

How do i set the storage and bandwidth limit on Azure for deployed application?

#Dec 16th, 2009 @ 12:43 PM
dunnry
dunnry

@jigneshpandya - In general, you don't set limits.  That is, you have some limits like 100TB of total storage (blobs, tables, queues) per storage account (up to 5 accounts by default).  Are you asking something else?

#Dec 24th, 2009 @ 8:22 AM
cbae
cbae

I just viewed the video on concurrency, and I was puzzled by the "golden ticket" approach to avoiding concurrency issues. If obtaining the golden ticket from the golden ticket queue is a requirement to process the messages in the request queue, then what is the point of having multiple instances of the worker role other than for fault tolerance? It seem as though this paradigm ensures that only one worker role is processing something at any given time, so in terms of processing time for all messages in the queue, this would be far less efficient than having just one instance of the worker role process.

#Jan 11th @ 11:46 AM
dunnry
dunnry

The whole issue with concurrency is to make sure that only one instance is processing the work.  The 'golden ticket' approach does not apply to work that can be done in parallel.  You would only use that approach when you wanted to ensure that something was done once and only once in an otherwise parallel environment.  Make sense?

Microsoft Communities