1. Scott Zimmerman Solutions Architect, SOA/.NET/Azure/BizTalk

2. Agenda Overview of Azure Services Platform Windows Azure Storage: Tables, Queues, BLOBs Compute: Web Role, Worker Role Azure Services Platform Infrastructure Getting Started Quick Tour Q&A

3. We’re running scale services now  2B Live Search queries/month  30B Live ID authentications/month  240B Messenger messages/month We’re building to run your services  $500 million per data center  10,000 servers/month

4. What’s in it for me? Suppose competitors A and B have similar systems to merge flat files from their branch locations each night, and display aggregate results in web applications. Both systems have an isolated operations cost (including administration, data management, computing, storage, security, power, and insurance) of $12,000/month. The CIO at Company A is converting her system to cloud computing. It will take 3 months to implement, at a cost of $13,000/month. Then her operations cost will drop to $1,000/month. Will she save money the first year? A: 3 * $12,000 + 3 * $13,000 + 9 * $1000 = $84,000 B: 12 * $12,000 = $144,000 Hypothetical savings = $60,000

5. Windows Azure is a cloud OS Scalability, Security, Interoperability Microsoft forecasts half of Exchange, SharePoint, and Dynamics CRM revenue coming from online versions within five years.

6. Accelerating Business Productivity Optimization Integrated, software- powered business communications Unified Communications Federated collaboration outside the firewall CollaborationCollaboration Business Productivity Online Suite Basic e-mail & traditional phone File Share collaboration and ad hoc teaming

7. Continuum of Services Cloud services have greater economies of scale, but less flexibility. S+S = Hybrid Approach In-House: Custom applications with competitive advantages; low latency required; firewall incompatible Azure- Hosted: Standard apps (Exchange, SQL, SharePoint); Distributed apps; Dynamically scalable apps

9. Write Applications for Windows Azure

10. Windows Azure Compute Web Role – Provides internet access to ASP.NET user interface or web service. Worker Role – Provides back-end computing service, e.g. number crunching.

11. Windows Azure: many design options Web Role Worker Role Queues, Tables, BLOBs UserApplication On Premise Cloud

12. Should every developer in your company start using cloud services? Azure Web Role BizTalk Server 2009 Compose, Aggregate, Transform, Connect, Publish, Monitor, Govern SharePoint SQL Server SiebelPeoplesoftSAPOracle Custom Apps… Geneva AD.NET Services Live Services Azure Storage SDS

13. Windows Azure Datacenter Your Service Windows Azure Architecture LB Internet Web Site (ASPX, ASMX, WCF) Web Site (ASPX, ASMX, WCF) Web Site (ASPX, ASMX, WCF) Web Site (ASPX, ASMX, WCF) Web Site (ASPX, WCF) Web Site (ASPX, WCF) Worker Service LB Storage Tables Blobs Queue

14. Windows Azure Storage Blobs – Provide a simple interface for storing files and metadata for the file. Tables – Provide structured storage. A Table is a set of entities, which contain a set of properties. Queues – Provide reliable storage and async delivery of messages for an application.

15. Account Container Blobs Table Entities Queue Messages Windows Azure Storage Concepts http://.blob.core.windows.net/ http://.table.core.windows.net/ http://.queue.core.windows.net/

16. Windows Azure BLOBs BLOBs are for storing files BLOBs consist of 1 or more blocks (of variable size you choose) Blocks provide continuation (in case of network failures) for BLOB upload Max block size <= 4 MB Max BLOB size <= 50 GB Containers can be “Public Read” or “Private” PutBlock… PutBlock… PutBlockList Blocks can go out of order and/or in parallel

17. Blob Storage Concepts BlockBlob Container Account sally pictures IMG001. JPG IMG002. JPG movies MOV1.AVI Block 1 Block 2 Block 3

18. Windows Azure Queues An Account can create many Queues Queue contains unlimited number of Messages Message is stored for at most a week Message Size <= 8 KB (point to BLOB or Table for more) When pulling a Message, specify InvisibilityTime InvisibilityTime <= 2 hours Messages should be IDEMPOTENT

19. Windows Azure Tables Provides Structured Storage Massively Scalable Tables Billions of entities (rows) and TBs of data Automatically scales to thousands of servers as traffic grows Durable Data replicated at least 3 times (in different domains) Familiar and Easy to use Programming Interfaces ADO.NET Data Services and LINQ –.NET 3.5 SP1 REST - with any platform or language

20. Windows Azure Table Capabilities What tables don’t do Not relational No Referential Integrity No Joins Limited Queries No Group by No Aggregations No Transactions CheapCheap Very Scalable FlexibleFlexible DurableDurable What tables can do

21. Table Data Model Table Each account can create many tables Just insert into a master table called "Tables“ (per account) Data is stored in Tables A Table is a set of Entities (rows) An Entity is a set of Properties (columns) Entity (row) Two “key” properties are together the unique ID of the entity in the Table PartitionKey – enables scalability RowKey – uniquely identifies the entity within the partition

22. Partition Key And Partitions Every Table has a Partition Key It is the first property (column) of your Table Used to group entities in the Table into partitions— for physical storage optimization A Table Partition All entities in a Table with the same partition key value

23. Partition Key Document Name Row Key Version Property 3 Modification Time …Property N Description Examples DocV1.08/2/2007…Committed version Examples DocV2.0.19/28/2007Alice’s working version FAQ DocV1.05/2/2007Committed version FAQ DocV1.0.17/6/2007Alice’s working version FAQ DocV1.0.28/1/2007Sally’s working version Partition Example Partition 1 Partition 2 Get all versions of FAQ Doc is fast (single partition) Get all documents before 9/1/2007 takes longer

24. Getting Started Example Use Cases 1. User: create workspace 2. User: submit string 3. User: get results 4. User: delete record 5. User: delete workspace Requirements 1. Employees at WorldWide Palindrome need to reverse strings. 2. They need a web page to submit strings to Windows Azure and view results.

25. UML Sequence Diagram Table Create Workspace Submit String Results Worker Role Web Role User Create Table Enqueue String Insert Reversed String View Results Query Queue Dequeue String

26. .NET or REST Use.NET 3.5 SP1 Data represented as.NET objects Use DataServiceContext methods for updates Use LINQ to define queries Richer error codes Use any HTTP stack Data represented in Atom (XML) Use HTTP verbs for updates Use URLs to define queries Standard HTTP errors ADO.NET Data ServicesREST Interface

27. Windows Azure Service Lifecycle Goal is to automate life cycle as much as possible Coding & Modeling New services and updates Provisioning Desired configuration Deployment Mapping and deploying to actual hardware Network configuration Maintain goal state Monitor React to events Automated Developer Developer/ Deployer

28. Fabric Controller (FC) Maps declarative service specifications to available resources Manages service life cycle starting from bare metal Maintains system health and satisfies SLA What’s special about it Model-driven service management Enables utility-model shared fabric Automates hardware management Windows Azure Automation “What” is needed Make it happen Fabric Switches Load- balancers Fabric Controller

29. Community Tech Preview (CTP) offers one virtual machine type Platform: 64-bit Windows Server 2008 CPU: 1.5-1.7 GHz x64 Memory: 1.7 GB Network: 100 Mbps Transient local storage: 250 GB Windows Azure storage also available: 50 GB Windows Azure Compute Instance

30. Fault domains are based on the topology of the data center Statistical in nature Update domains are determined by what percentage of your service you will take out at a time for an upgrade System considers fault domains when allocating service roles System considers update domains when upgrading a service Fault/Update Domains Allocation is across fault domains Fault domains

31. Getting Started 1. Please visit Azure.com 2. Get a token 3. Install SDK 4. Read white papers 5. Watch PDC and MIX videos 6. Get sample code in “Azure Training Kit” 7. Create your application

32. Quick Tour

33. Q & A 1.Please visit Azure.com 2.Get a token 3.Install SDK 4.Read white papers 5.Watch PDC and MIX videos 6.Get sample code in “Azure Training Kit” 7.Create your application