Windows azure storage devcon2011
•Télécharger en tant que PPTX, PDF•
1 j'aime•543 vues
Presentation given on Windows Azure Storage at Dev Con 2011 at Microsoft Hyderabad on 1st Oct, 2011
Recommandé
Contenu connexe
En vedette
Similaire à Windows azure storage devcon2011
Similaire à Windows azure storage devcon2011 (20)
Dernier
Dernier (20)
Windows azure storage devcon2011
- 1. Developer Conference 2011 MICROSOFT USER GROUP HYDERABAD
- 2. Windows Azure Storage Charan Kawal Singh Bhatia Lead Developer bhatiack@gmail.com
- 3. Virtual Machines Compute Database Caching Storage CDN Service Bus Virtual Network Access Control Business Intelligence
- 5. Storage in the Cloud
- 6. Windows Azure Storage Demo Creating a Storage Account
- 7. Storage in the Dev Fabric
- 8. What is Blob Storage
- 9. Windows Azure Content Delivery Network
- 10. Windows Azure CDN User in Europe requests Web page Deploy hosted service and storage to cloud (North Central US) Web page delivered from US... Content requested from nearest datacenter. Enable CDN for Web page content Content unavailable, retrieved from US MyVideo 6. Content is cached in Dublin datacenter Watch videos of dogs and cats doing funny things! Vote for your favorite, or submit your own! 7. 2nd user in Europe requests Web page 8. Web page delivered from US, content delivered from Dublin Microsoft Datacenter
- 11. Windows Azure Demo Blob Storage
- 13. Table Storage
- 15. Table Data Model
- 16. Partitions and Partition Ranges Server A Table = Movies [MinKey - Comedy) Server A Table = Movies Server B Table = Movies [Comedy - MaxKey)
- 17. Queues Worker Worker Worker Worker Web Web Web
- 18. Demo Windows Azure Storage
- 19. Some Links http://www.microsoft.com/windowsazure/ http://www.microsoft.com/windowsazure/sdk/ http://www.microsoft.com/download/en/details.aspx?id=8396 {Training Kit} http://www.microsoft.com/windowsazure/community/ {Community}
- 20. ?
- 21. Thank You
- 22. Sponsors
Notes de l'éditeur
- There are multiple feature as of now available in the Windows Azure platform.Compute: Web and Worker roles to host applications around the world.Database: Highly available and scalable relational cloud database services as SQL AzureVirtual Machines: Where you can deploy your custom windows Server 2008 R2 images to windows Azure.CDN (Content Delivery Network): Deliver high-bandwidth content through 24 global physical nodes.Caching: Distributed, in-memory application cache service.Virtual Network: Networking functionality to connect on-premises and cloud applications.Service Bus: Secure messaging capabilities for distributed and hybrid applications.Access Control: Standards-based service for identity and access control.Business Intelligence: Develop and deploy operational reports to cloud using familiar tools.Storage: Windows Azure gives you four core storage services that are secure, scalable and easy to access that remain persistent and durable storage in the cloud. Blobs, Tables, and Queues are all available as part of the Windows Azure Storage account, and provide durable storage on the Windows Azure platform. Unlike local storage, blobs, tables, and queues are accessible by multiple applications or application instances simultaneously, and represent dedicated storage instead of temporary.
- 1. Windows Azure gives you four core storage services that are secure, scalable and easy to access that remain persistent and durable storage in the cloud. Blobs, Tables, and Queues are all available as part of the Windows Azure Storage account, and provide durable storage on the Windows Azure platform. Unlike local storage, blobs, tables, and queues are accessible by multiple applications or application instances simultaneously, and represent dedicated storage instead of temporary.2. Easy to use REST and Client Libraries:I’mnot going to describe the REST architecture here. All storage services are accessible via REST APIs. Storage services may be accessed from within a service running in Windows Azure, or directly over the Internet from any application that can send an HTTP/HTTPS request and receive an HTTP/HTTPS response. You can access three services from REST (Blob service, Queue Service, and Table service). Highlights of Windows Azure StorageBinary Large Object (BLOB) Service, the simplest way to store text or binary data with Windows Azure.Table Service is better for large amounts of data that need additional structure, which works exceptionally well with applications that need to work with data in a very detailed manner via queries.Queue Service for reliable, persistent messaging between Web and Worker role instances.Windows Azure Drive allows Windows Azure applications to mount a Page Blob, which is a single volume NTFS VHD. This allows applications to upload/download VHDs via blob.New features (09/16/2011)Windows Azure Geo-replication replicates Windows Azure Blobs and Tables between two data centers 100s of miles apart from each other on the same continent, at no additional cost, to provide additional data durability in the case of a major disaster. Table Upsert allows a single request to be sent to Windows Azure Tables to either insert an entity (if it doesn’t exist) or update/replace the entity (if it exists). Table Query Projection (Select) allows a client to retrieve a subset of an entity’s properties. This improves performance by reducing the serialization/deserialization cost and bandwidth used for retrieving entities. Improved Blob HTTP header support improves experience for streaming applications and browser downloads.Queue UpdateMessage allows clients to have a lease on a message and renew the lease while it processes it, as well as update the contents of the message to track the progress of the processing.Queue InsertMessage with visibility timeout allows a newly inserted message to stay invisible on the queue until the timeout expires.
- Show the demo on http://windows.azure.comCreate the Storage Account from the site.Show the endpoints of Blob/Table/Queue and also tell the purpose of each endpoints.Show the primary Keys and Secondary Keys and explain.CDN: Just show it at high level. There is another slide on it and will be cover more in detail over there.
- Show the demo on http://windows.azure.comCreate the Storage Account from the site.Show the endpoints of Blob/Table/Queue and also tell the purpose of each endpoints.Show the primary Keys and Secondary Keys and explain.CDN: Just show it at high level. There is another slide on it and will be cover more in detail over there.
- It is not required to connect to the windows storage account online during the development time. As we know each and every transaction is counted in an account. Therefore, Windows Azure SDK provides Local Mock Storage. There are Store Emulator which allows the developers to do the offline development.There are Emulators for Blob, Table, Queues which allows the offline development.Show the user about Emulators: Storage and Compute both.Explain how the user can do the offline development with the storage.
- BLOB is Binary Large Object.These are data/files stored in the containers. Containers are just like directories which are used to categorize the BLOBs.The Metadata of the BLOBs are in the form of name / value pair.When we want to store the media files into the Blob Storage, they are stored in Block Blob. It is faster than Page Blobs. It is mainly designed for the streaming of data of max size 200 GB.The another type of blob is the Page blobs where we can store the images, files etc. These Page Blobs are mainly designed for the read/write operations having the max size of 1 TB.
- PartitionKey – The first key property of every table. The system uses this key to automatically distribute the table’s entities over many storage nodes.RowKey – A second key property for the table. This is the unique ID of the entity within the partition it belongs to. The PartitionKey combined with the RowKey uniquely identifies an entity in a table. The combination also defines the single sort order that is provided today i.e. all entities are sorted (in ascending order) by (PartitionKey, RowKey).Timestamp – Every entity has a version maintained by the system which is used for optimistic concurrency. Update and Delete requests by default send an ETag using the If-Match condition and the operation will fail if the timestamp sent in the If-Match header differs from the Timestamp property value on the server.Entity Group TransactionsEntity Group Transaction provides atomic transaction over a group of entities in a single table that have the same PartitionKey value. Here are the rules for Entity Group Transactions:A single batch transaction can have up to 100 entities.Request size for a batch transaction should not exceed 4MB in size.In a single batch transaction, an entity cannot repeat itself (i.e. the RowKey property should be different).