2. About me
⢠More then 10+ years of experience in Microsoft.NET and related
technologies
⢠Currently working as Project Manager at TatvaSoft
⢠Have been Awarded as Microsoft Most Valuable Professional
(Visual C#) for year 2010,2011 and 2012.
⢠Frequently writing blogs about Microsoft.NET and related
technologies at my blog http://www.dotnetjalps.com
⢠Also awarded as Dzone Most Valuable Blogger.
⢠Active Member of Ahmedabad .NET User Group.
3. Windows Azure Storage
⢠Cloud Storage, Any time any where access
⢠Durable and Highly available
⢠Pay for what you use
⢠Massively Scalable â Easily build internet scale enterprise level application
- 35 trillion plus + Storage options
- 3.5 million request + Request/sec on average
⢠Azure Storage uses an auto-partitioning system that automatically load-
balances your data based on traffic
⢠Exposed via Rest APIs or Also Client Libraries are available in languages like
.NET, Java and Node.js.
⢠Azure storage is accessible from any platform like desktop, Web or devices
4. Azure Storage Account
⢠An Azure storage account is a secure storage account that
gives access to services in Azure Storage
⢠Two types of accounts
- Standard
- Premium
⢠Standard Storage account Include all the Azure Storage
Abstractions (Blob, Table, Queue and File Storage)
⢠Premium Storage account supports Azure Virtual Machine
disks(SSDs) only right now
18. ⢠Azure Queue storage is a service for storing large
numbers of messages that can be accessed from
anywhere in the world via authenticated calls using HTTP
or HTTPS.
⢠A single queue message can be up to 64 KB in size,
and a queue can contain millions of messages, up to
the total capacity limit of a storage account.
⢠A storage account can contain up to 500 TB of blob,
queue, and table data.
Queue details
19. ⢠Common Usage of Queue Storage Includes
⢠Creating a backlog of work to process asynchronously
⢠Passing messages from an Azure Web role to an Azure Worker role
⢠Queues are accessible from following URL format
⢠http://<storage account>.queue.core.windows.net/<queue>
⢠A Queue contains messages and a message can be
maximum of 64 Kb of size
Queue details
23. ⢠Microsoft Azure virtual machines and cloud services can share file
data across application components via mounted shares, and on-
premises applications can access file data in a share via the File
storage API.
⢠File storage offers shared storage for applications using the
standard SMB 2.1 protocol.
⢠Applications running in Azure virtual machines or cloud services
can mount a File storage share to access file data, just as a desktop
application would mount a typical SMB share. Any number of Azure
virtual machines or roles can mount and access the File storage
share simultaneously.
Azure Files
24. ⢠Since a File storage share is a standard SMB 2.1 file share,
applications running in Azure can access data in the share via file I/O
APIs. Developers can therefore leverage their existing code and skills
to migrate existing applications.
⢠Common uses of File storage include
- Storing shared application settings, for example in configuration files
- Storing diagnostic data such as logs, metrics, and crash dumps in a shared location
- Files that is accessible via multiple locations
⢠Files are addressable using the following URL format
- https://<storage account>.file.core.windows.net/<share>/<directory/directories>/<file>
Azure Files
32. Two Types of Blobs Under the Hood
â˘Each block can include MD5 hash to verify the Transfer,
so you can track upload progress and resend blob storage
if required
Block Blob:
Slide Objectives
Understand Tables and Entities
Speaker Notes
Tables store data as entities.
An entity is a collection of named properties and their values, similar to a row- not an RDBMS though
Tables are partitioned to support load balancing across storage nodes.
Each table has as its first property a partition key that specifies the partition an entity belongs to.
The second property is a row key that identifies an entity within a given partition.
The combination of the partition key and the row key forms a primary key that identifies each entity uniquely within the table.
The Table service does not enforce any schema.
A developer may choose to implement and enforce a schema on the client side
Notes
http://msdn.microsoft.com/en-us/library/dd573356.aspx
http://msdn.microsoft.com/en-us/library/dd179338.aspx
Slide Objectives
Understand Tables
Speaker Notes
The Table service provides structured storage in the form of tables.
The Table service supports a REST API that is compliant with the ADO.NET Data Services REST API.
Developers may also use the .NET Client Library for ADO.NET Data Services to access the Table service.
Notes
http://msdn.microsoft.com/en-us/library/dd573356.aspx
Slide Objective
Understand block blob
Speaker Notes
Block blobs are comprised of blocks, each of which is identified by a block ID.
You create or modify a block blob by uploading a set of blocks and committing them by their block IDs.
If you are uploading a block blob that is no more than 64 MB in size, you can also upload it in its entirety with a single Put Blob operation.
When you upload a block to Microsoft Azure using the Put Block operation, it is associated with the specified block blob, but it does not become part of the blob until you call the Put Block List operation and include the block's ID.
The block remains in an uncommitted state until it is specifically committed. Writing to a block blob is thus always a two-step process.
Each block can be a maximum of 4 MB in size. The maximum size for a block blob in version 2009-09-19 is 200 GB, or up to 50,000 blocks.
Notes
http://msdn.microsoft.com/en-us/library/dd135734.aspx