Lap around the Windows Azure Platform - ericnel


Published on

Overview session delivered at uktechdays 5th Oct 2010. This was a jam packed 45min session.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Lap around the Windows Azure Platform - ericnel

  1. 1. Lap around the Windows Azure Platform Eric Nelson | ISV Application Architect | Microsoft UK | | Page 1
  2. 2. Assumption • Most of you are pretty new to the Windows Azure Platform • If you are not, check out: – – – Including two weeks of free training • Starting October 11th – And three track online conference • October 8th Page 2
  3. 3. Agenda Overview of the Windows Azure Platform • Overview of the platform • Compute • Data • SQL Azure Labs Summary and Next Steps Page 3
  4. 4. Overview Page 4
  5. 5. Windows Azure Platform makes it easy and cost effective to run your applications and store your data inside Microsoft Data Centres using existing skills and integrate with your existing on-premise applications Page 5
  6. 6. Windows Azure Platform Page 6
  7. 7. You do most of your development locally Page 7
  8. 8. Your code runs in Hosted Services made up of Roles Page 8
  9. 9. Your Roles are code + configuration Page 9
  10. 10. You choose which type(s) of Role to run your code in Page 10
  11. 11. At runtime you can have multiple instances of your Roles Load Balancer Page 11
  12. 12. You store your data in Windows Azure Storage Page 12
  13. 13. And/or you store your data in SQL Azure Page 13
  14. 14. Demo Page 14
  15. 15. Bringing it all together Single Billing Azure Account Relationship Subscription 1 Subscription 2 Subscription 3 ….. Windows Market Azure App Fabric SQL Azure Place Hosted Storage Services SQL Azure http://yourapp1.clou http://yourapp2.clou http://yourstorage1. http://yourstorage2. Server t/ t/ DB DB Web Role Worker Queue Table Blob Drive Role Page 15
  16. 16. You have many choices for data Relational Database Structured Storage Unstructured Storage NTFS Drive Service Communication Page 16
  17. 17. Side by Side Evaluation Single SQL Single Blob Drive Queue Table Azure Database Structured Data Y Y Relational Database Y Server Side Processing Y Direct Access from outside Y Y Y Y Azure Messaging Infrastructure Y Persistent Storage Y Y 1 week Y Y 200 GB/ 1 Size Limit 1 TB 100 TB 100 TB 50 GB (*) TB Page 17
  18. 18. SQL Azure Labs Page 18
  19. 19. Demo Page 19
  20. 20. Summary • Very easy to get going… but lots to learn • Plenty of early adopters, therefore – Good best practice are now appearing – Plenty of detail to dig into • Lots more coming Page 20
  21. 21. NEXT STEPS For latest slides and all the links For more resources and information As an ISV intending to explore/adopt azure, sign up to and come along and meet with us Eric Nelson | ISV Application Architect | Microsoft UK | | Page 21
  22. 22. Screens Page 22
  23. 23. SQL Azure Labs Page 23
  24. 24. OData Page 24
  25. 25. OData Page 25
  26. 26. Data Sync Page 26
  27. 27. Data Sync Page 27
  28. 28. Data Sync Page 28
  29. 29. Data Sync Page 29
  30. 30. Houston Page 30
  31. 31. Houston Page 31
  32. 32. Houston Page 32
  33. 33. Appendix Page 33
  34. 34. Azure Drive (X-Drive) • Access to a Local Drive in Azure • Enables existing applications using NTFS to easily migrate to the cloud • Essentially a Page Blob formatted as NTFS – Remote Access via Page Blob Interface • Durable NTFS volume [upto 1TB] for Windows Azure Applications • Drives in the Cloud are only mountable by VMs within Cloud – Mounted by one VM at a time for read/write – A VM can dynamically mount up to 16 drives Page 34
  35. 35. Azure Drive - Scenario • The Application Mounts a Drive • Mount obtains a Blob Lease Application • Mount specifies size of Local Cache • NTFS Writes update the Drive – Blob Store & then the Local Cache X: • NTFS Reads can be served from – Local Cache or – Blob Store (cache miss) Local Cache Lease Page Blob Azure Drive Page 35
  36. 36. Azure Table and SQL Azure Table Feature Azure Table SQL Azure Table Partitioning Implicit based on Partition Key Explicitly managed by the Application & Scale (Sharding – future feature) Table indexed on Partition Key + Row Index 1 Clustered Index on any column Key Capabilities 999 Secondary Indexes 0 Secondary Indexes Row Size – 1 MB Row Size – 8MB Table Limits Column Limit – 255 Column Limit – 1024 Table Limit – 100TB Table Limit - ~50GB Transactions on entities within partition Fully compatible transactional semantics No Transactions across tables or with SQL Server. Transactions partitions Up to 100 operations in a Transaction No cross Database transactions Payload upto 4MB per Transaction Consistency Transactionally Consistent Transactionally Consistent Model Full range of isolation and concurrency Concurrency Single Optimistic Concurrency Strategy models as supported by RDBMS Page 36
  37. 37. Azure Table and SQL Azure Table Feature Azure Table SQL Azure Data Standard tools and APIs apply REST API, ADO .NET, Client Library SDK Access SSMS, Visual Studio, ADO .NET, ODBC Column Basic Types Usual SQL Server Data Types Types Data in SQL Azure similar to SQL Server - Easy migration in and out of the Data portability coming with Windows Azure Portability cloud Appliance - Use multi stream transfer to mitigate network latency. Query capabilities as per standard SQL Upto 1000 entities [token pagination] Server database expectations Beyond 5 sec – return continuation token Offer Server Side Processing through Queries Queries by partition & row key are fast Stored Procedures and Complex Queries No Custom Indexes Today Non key queries are scans (Aggregation, Joins, Sorts, Filters, etc.) Page 37