1. Windows Azure Building web sites and services in the cloud Manu Cohen-Yashar Sela Group http://blogs.microsoft.co.il/blogs/applisec

2. Agenda Why cloud services Windows azure Main programming elements Demo Q & A Summary

3. Why cloud services

4. Service Isolation Exception Configuration Failed Message Management Message Tracking Composite Execution Tracking Composite State Management Load Balancing Fail-over Throttling Scale-out Configuration Identity & Impersonation Configuration Management Multi-environment Deployment Model Availability Monitoring Health Monitoring Utilization/Performance Tracking Disaster Recovery Archiving & Purging Regulatory Compliance Scripting & Programmability APIs Memory Management Thread Management

5. Scalability LB

6. Scalability in another dimation

7. Azure ™ Services Platform

8. A Look Inside Azure Service Bus Access Control Workflow … … Database Reporting Analytics … … Compute Storage Manage Identity Devices Contacts … … … … … … Your Applications

9. ACCESS CONTROL

10. Access Control Your Customers Your App Access Control Service Live ID Users XYZ Domain Users Who is the caller? What can they do? UI Integrate Service Bus Orchestrate Store WF Data

11. Access Control Moving Parts Portal – A UI for creating and managing collections of access control rules Client API – Provides a programmatic way to manage collections of access control rules Service (STS) – A hosted service that issues tokens – Developers interact with the service via the “Geneva” Framework

12. Access Control Interactions Your.NET Access Control Service STS (Managed STS) Your.NET Access Control Service STS (Managed STS) Relying Party (Service Bus, Your App, etc.) Relying Party (Service Bus, Your App, etc.) 2. Send Claims (RST) 4. Send Token (RSTR) (output claims from 4) 5. Send Message w/token 0. Cert|Secret exchange; periodically refreshed Requestor (Your Customer) Requestor (Your Customer) 1. Define access control rules for a customer 6.Claims checked in Relying Party 3. Map input claims to output claims based on access control rules

13. SERVICE BUS

14. Enterprise Service Bus Service Orchestration Service Orchestration Service Registry Naming Federated Identity and Access Control Messaging Fabric CRMCRM Customers Leads Trends Campaigns Supply Chain Inventory Order Entry Planning Purchasing Point Of Sale POS Integration Product Catalog Returns Web Store

15. Internet Service Bus Service Orchestration Service Orchestration Service Registry Naming Federated Identity and Access Control Messaging Fabric ClientsClients MS/3 rd Party Services MS/3 rd Party Services On-Premise ESB ESBESB Desktop, RIA, Web Desktop, RIA, & Web Your Services

16. SERVICE ORCHESTRATION

17. Your Own Host Your Own Host “Dublin”.NET Workflow Service Hosting WF WF

18. Service Orchestration http:// Service Bus

19. SQL DATA SERVICES

20. SQL Services Futures Extending the SQL Data Platform to the cloud Reference Data Reporting ETL Data Mining Data services tier of the Azure Services Platform Built on SQL Server foundation Broad data platform capabilities as a service – Friction-free provisioning, scaling – Significant investments in scale, HA, lights-out operation and TCO

21. SDS is built on three key pillars 1.Storage for all data types from birth to archival 2.Rich data processing services 3.Operational excellence SQL Data Services (SDS) “Database as a Service”

22. Trey Research Media Marketplace Photo Management WPF App Photographer In Field Mobile App

24. It is an operating system for the cloud It is designed for utility computing It has four primary features: – Service management – Compute – Storage – Developer experience What Is Windows Azure? What Is Windows Azure?

25. The same facilities that a desktop OS provides, but on a set of connected servers: – Abstract execution environment – Shared file system – Resource allocation – Programming environments Utility computing – 24/7 operation – Pay for what you use – Simpler, transparent administration What Should The Cloud OS Provide?

26. The Windows Azure provides core technologies for building rich services on top of unreliable but scalable hardware (i.e., a cloud operating system) – Supports building applications that scale – Programming tools and interfaces are designed to be familiar to traditional desktop programmer Introduce new concepts that are similar to existing ones at a different abstraction level Windows Azure

27. Desktop And Related Azure Concepts Desktop EXE Application Configuration Manifest DLL – Windows forms library – Windows service Local data stores Windows Azure Service package Service configuration Service definition Service role – Web role – Worker role Internet data stores

28. Service definition – Defines aspects of a service that cannot be changed without redeployment Types of roles and static role configuration Set of configuration settings for a role Contract with the environment code runs Service configurations – Defines values for properties that can be dynamically updated for a running deployment Values of a configuration parameter Number of running instances Service Concepts

29. Storage Services Web Role Web farm that handles request from the internet IIS7 hosted web core – Hosts ASP.NET – XML based configuration of IIS7 – Integrated managed pipeline – Supports SSL Public Internet Web Role Load Balancer

30. Worker Role No inbound network connections Can read requests from queue in storage Storage Service Public Internet Worker Role

31. Every role has access to APIs for common functionality needed for services – Read configuration setting values – Write messages to set of standard logging streams “Printf” sitting on top of a lot of plumbing so logs are downloadable and archived easily Critical messages generate live alerts – Get access to unreliable local storage for caching Defines interface for worker role Service Runtime API

32. RoleEntryPoint For Worker Role public abstract class RoleEntryPoint { //Constructors protected RoleEntryPoint(); //Methods … public abstract RoleStatus GetHealthStatus(); public abstract void Start(); … } public enum RoleStatus { Healthy …, Unhealthy, … }

33. Blobs – provide a simple interface for storing named files along with 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 delivery of messages for an application Windows Azure Storage Abstractions

34. Block Blob Storage Concepts Key concepts account, container, blob, and blocks BlobContainerAccount Pictures IMG001.JPG IMG002.JPG MoviesMOV1.AVI Block AAAA Block AAAB Block AAAC

35. Queue Storage Concepts Account, queue, and message MessageQueueAccount Thumbnail Jobs 128x128, http://… 256x256, http://… Indexing Jobs http://…

36. Table Storage Concepts Account, table, and entity EntityTableAccount Users Name=…hash=… PhotoIndex Tag=…id=… Tag=…,id=…

37. Every table has a partition key – It is the first property (column) of your table – All entities in a table with the same partition key value live in the same partition Need to choose partitioning scheme to make data access scalable Partition Key and Partition

38. DEMO Building your first application

39. Summary The hosting problem Windows azure platform enables you to concentrate on your business logic A new programming model – Web role – Worker role – Blobs, Tables and queues

40. Additional Resources www.azure.com http://www.microsoftpdc.com/

42. © 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.