1. Michael Stiefel Reliable Software, Inc. Microsoft Corporation development@reliablesoftware.com http://www.reliablesoftware.com/dasblog/default.aspx

2. What is the cloud?

3. Computation can be a utility.

4. Azure is a cloud operating system.

5. An operating system: abstracts the underlying infrastructure manages resources

7. Windows Azure primary features: Service management Compute Storage Developer experience

8. You define rules and provide code Platform deploys, monitors, and manages your service according to your rules

9. All of the hardware: servers; load balancers; etc… Virtualized and direct execution

10. Blobs Tables Queues

12. Cloud Storage (blob, table, queue) Web Role LB n Worker Role m

14. What’s in the model? Service topology and size Health constraints Configuration settings Develop and Model Deploy and Run Maintain Service Health

15. Logical resources declared in the service model Platform APIs map logical resources to physical entities Service code then uses these APIs

16. Operating System can replace resources transparently: Failures Upgrades Scaling

17. A balance between power and ease of use Write well behaved services, reduce your TCO Designed for a full range of scenarios, from the hobbyist to the enterprise developer But there is an escape hatch … In “Raw” mode, you can build your own VM and manage the service yourself

19. A cloud environment on the desktop Support for a variety of programming languages ASP.NET,.NET languages, native code, PHP An ecosystem of tools and support Integration with Visual Studio, Eclipse Logging, alerts, tracing, … Samples, documentation, MSDN, forums, …

20. Developer Experience Service Hosting Service Management  Consistent with on- premises  Standard support - REST & SOAP  Support for 3rd party languages Coming soon  Scalable (elastic)  Flexible  Secure & Reliable  Tracing & logging  Upgrade service w/o downtime  Real-time monitoring & metering

21. Azure Services Platform

22. Familiar tools, languages, and frameworks with.NET and Visual Studio Provides the choice to build on-premises, cloud, or hybrid solutions Integrate with existing assets such as AD and premises applications Multiple protocol support including HTTP, REST, SOAP, AtomPub Broad investment in open, community-based access to Azure services Simple scenarios are simple – complex scenarios are possible Services hosted in Microsoft’s data centers Designed for high availability & scalability

23. Azure ™ Services Platform

25. .NET Services Access Control Workflow Service Bus Support user identities securely across different organizations Model and execute business logic and service interactions Exchange messages between loosely coupled, composite applications  Claims-based identity management  Interoperable & based on standard protocols (WS- Trust)  Manage through web page and/or a services API  Supports CardSpace, LiveID, Username/Password  Runtime execution environment for XAML-based workflows  Enables the orchestration of services  Extension of Windows Workflow Foundation  XAML-based models can be uploaded to the cloud  Simple publish-subscribe eventing  Firewall friendly messaging  Flexible connection modes  Connectivity to on-premises applications to enable hybrid S+S scenarios  Extension of Windows Communication Foundation

26. Extending.NET technologies to the cloud Open and accessible REST, SOAP, RSS, AtomPub, … Class libraries for Java, PHP, Ruby, … Easy-to-use from.NET – skills move forward Initial focus on three key developer challenges Application integration Access control in a federated world Application extensibility

28. Key developer challenges Many identity providers, many vendors, many protocols, complex semantics – tricky to get right Application strewn with one-off access logic Hard to get right, not agile, not compliant, many dead ends Approach Automate federation for a wide-range of identity providers and technologies Factor the access control logic from the application into manageable collection of rules Easy-to-use framework that ensures correct token processing

29.  These all use same approach to access control: Microsoft SQL Data Services o Accepts both a Username & Password and a token produced by.NET Access Control Service.NET Service Bus.NET Workflow Service The Portals

30. .NET ServiceBus,.NET Workflow Service and Microsoft SQL Data Services have.NET Access Control Service accounts.  These accounts contain scopes and encryption preferences.  Rules are automatically added to scopes when new customer accounts are created.  The rules are different for the.NET Service Bus,.NET Workflow Service, and the Microsoft SQL Data Service.  The.NET Service Bus and.NET Workflow Service grant customer accounts edit permissions based on the rules.

31. Your Enterprise Adventure Works *Hosted or self-hosted Sandy@hotmail.com Lane@Litware.com ASP.NET Contoso SAP Cory AD Mail Fabrikam Francis AD “Geneva”Services Connector Azure™ Services Access Control Mesh Service Bus Service Bus Workflo w LiveID SQL Data

32. 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

33.  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  Secure Token Service (STS)  A hosted service that issues tokens  Developers interact with the service via the “Geneva” Framework

34.  Flexible, rules-driven access control  Rich support for a wide range of identity providers  The Geneva framework is the.NET developer experience  Easy to incorporate into existing applications  Works with lots of other environments; e.g. Sun’s Java Metro 1.3, …

36.  Key developer challenges  Want to make it easy and secure for partners to use your application  Don’t always know the characteristics or scale of the integration  Partners / customers / users have devices and services running behind firewalls  Approach  Provide a high-scale, high-available “Service Bus” that supports open Internet protocols

37. 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

38. 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

39.  The Internet Service Bus pattern  Service Registry  Connectivity (Relay & Direct Connect)  Publish/Subscribe  Nitty Gritty  Bindings  Ensuring connectivity  Integration with Access Control

40. [http|sb]://servicebus.windows.net/services/account/svc/… Root servicebus. windows. net services account contoso … … svc Service Registry Root Multi-Tenant The service registry provides a mapping from URIs to services

41.  Two key capabilities  Relay  Direct connect  Relay  Ensure applications connect  Available to all via the service registry  Direct connect  Uses the relay to establish communication  Then shortcuts for efficiency  Available via HTTP / REST / ATOM  Available in.NET via WCF Bindings

42. Relay sb://servicebus.windows.net/services/user/service/endpoint Sender Receiver Outbound SSL-Secured TCP 828 Connection to Relay Rendezvous Endpoint One-Way Messages through TCP Tunnel

43. Relay sb://servicebus.windows.net/services/user/service/endpoint SenderReceiver - Outbound SSL-Secured TCP 828 Connection to Relay - Out-of-Band Protocol to negotiate Direct Connection Upgrade to Direct when possible

44.  Builds on the relay and direct connect connectivity capabilities  Initial release is “connected multicast”  Over time will provide additional delivery characteristics – anycast, reliable, …

45. Relay sb://servicebus.windows.net/services/user/service/endpoint Sender Receiver Outbound SSL-Secured TCP 828 Connection to Relay Rendezvous Endpoint One-Way Messages through TCP Tunnel Receiver

46.  Service Registry  Relay and direct connect connectivity  Publish/Subscribe  Integrated with Access Control services

48.  Key developer challenges  Want to easily describe long-running processes  Want modularity and nesting  Easy to describe but in practice harder to run ▪ Hosting and scaling can be challenging ▪ Setup and installing, define scale-out approach, ensure long-running availability, manage upgrades, …  Approach .NET 3.0/3.5/4.0 addresses key developer requests .NET Services makes it easy to deploy, manage and run Workflows

49. WF Runtime  Easily describe coordinated work with minimal ceremony  Tools/Designers  Activity Library  Runtime  Hosts Tooling VS Designer VS Debugger Re-hosted Designer Workflow Activity Library IIS/WAS+ “Dublin” IIS/WAS+ “Dublin” Workflow Service Workflow Service your.exe “Direct” your.exe “Direct” Hosts

50.  A portal at workflow.ex.azure.microsoft.com  New activities for the Azure Services Platform  APIs that allow you to deploy, manage, and run your workflows on the cloud  Enables you to orchestrate services  Connect to services in your enterprise anywhere on the Internet – uses the connectivity services  Give you partners and customer access – uses the access control services A reliable, scalable, off-premises, host for workflows

51. 1. Design Workflows  Choose WF Model  Use a WF Designer  Use new Azure activities and a subset of WF out- of-the box activities 2. Deploy Workflows  Upload and validate 3. Manage Workflow Types  Add, delete, update, view instances 4. Manage Workflow Instances  Create, run, control, track execution

52. Workflow & Rules XAML 11 Visual Studio WF Designer Your Apps & Services http:// ServiceBusServiceBus Workflow PortalWorkflow Portal WorkflowClient APIWorkflowClient API SOAP Web ServiceSOAP Web Service Workflow PortalWorkflow Portal WorkflowClient APIWorkflowClient API SOAP Web ServiceSOAP Web Service 22 3344 Design Workflows 11 Deploy Workflows 22 Manage Workflow Instances 44 Manage Workflow Types 33 22 VS – one click deploy

53.  Execute Workflows with high availability  Design Workflows using existing tools  Easily deploy and manage Workflows  Portal for easy access  Management APIs for rich automation

55. WINDOWS AZURE STORAGE  “Essential storage service in the cloud”  Provides a core set of non- relational storage and retrieval abstractions at massive scale SQL DATA SERVICES  “Premium database service in the cloud”  Extends the rich capabilities of the SQL data platform to the cloud at scale  Relational data processing over structured and unstructured data  Integrate with key data platform capabilities – e.g. Data Analytics, Reporting, ETL

56. Developer Agility Scalability and Flexibility Reliability and Security  Relational queries  Blobs  XML wire format  SOAP and REST support  Data partitioned for throughput and unlimited Scale  Transactional Consistency.  Flexible data model - no enforced schema  Built using Microsoft SQL Server technology  Authentication & Authorization  Backup and geo- distribution for Business Continuity SQL Services

57. 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

58.  We’ll focus on  Data model/access  Occasionally connected  Business intelligence Mobile/Desktop OLAP FILE XML RDBMS Query Analysis ReportingIntegration Sync Search Server Data Services

59.  Line of Business Applications Delivered as a Service  Collaborative Web Applications  Shared Data Hub  Data Warehousing and Business Intelligence

60.  Authority  Unit of geo-location and billing  Server, Tied to DNS Name  Container  Unit of consistency/query (DB)  Collection of entities  No schema required (no metadata)  Entity  Property bag of name/value pairs  Unit of update/change (rows)  Flexible shape and types

61. Entity properties may differ in type and instance: Different Instance Types Additional Property

62. Container X SDS Back End SDS Front End

63.  SQL Data Services (SDS) has been architected for flexible use within your future software+service application architectures  SDS is being extended in many important directions, revealing the full power of SQL Server and the SQL Server data platform in the cloud  Relational capabilities  Data model  Alignment to ADO.NET Data Services conventions  Data Synchronization  SQL Server platform capabilities like BI

64. Azure Services Management Tools: http://code.msdn.microsoft.com/AzureManagementTools

66. … are a set of building blocks for handling user data and application resources which can connect your application to hundreds of millions of users. Mesh Services 1.2B 30B 367M 320M nnPB 460M

67. Jump Start Traffic Embed Social Building Blocks Connect across Devices  460+ Million people on Windows Live  Comprehensive Windows Live services API’s (incl. Messenger, feeds, contacts, search)  Developer Tooling with integrated Live Services  Open, interoperable programming interface and resource model across PC, Phone and Web  Data synchronization and local accessibility across many end points Live Services

68.  Cloud/Client/Device reach  Access to user-data  Application ecosystem  Easy to get started

69.  Live fx is the uniform way to program Live Services  Any platform,  Any programming language  Any application or device  Live fx makes it easy to build software + service applications .NET developers can use the Live fx API kit to build applications

70.  Integrate Live Services into your applications  Opt in to as much of the Live Framework as you like  Expose your application as Mesh Applications

71. Bring exciting new devices into the Mesh, integrate with core infrastructure and experience Seamlessly integrate social applications across invites, news feeds, local devices experiences, and more Take your web application and content to the client, enable a rich and seamless offline experience Service-enable client applications, make them Mesh-aware, enable multi-user sharing-based experiences World of Devices Social and Community Sites Client-to- the Web Web-to- the Client

72.  Live fx is the uniform way to program Live Services  Any platform,  Any programming language  Any application or device  Live fx makes it easy to build software + service applications .NET developers can use the Live fx API kit to build applications

74.  Operating system for the cloud  Designed for utility computing  Four primary features:  Automated service management  A powerful service hosting environment  Scalable, available cloud storage  A rich, familiar developer experience  Designed to encourage best practices:  Stateless compute + durable storage  Co-location of computation and data  Queues for asynchronous processing  An open platform  Connect outbound to any server  Open protocols and APIs on all components

75. It’s about “The Power of Choice…” Extend existing On-Premise Application Deploy Complete Application in the Cloud Compose New Application from Cloud Services

76. PDC2009Future Compute Simple Storage Developer Tools Native Code Support Advanced logging and tracing Dynamic Scaling Variable VM sizes Global datacenter presence Support for Windows Server VM’s 3rd party open standards support, e.g. PHP, Ruby, Python, Eclipse Services Library/ Marketplace Query support for Joins, Top, OrderBy Simple Data Model Transactional Consistency Data Protection Rich data types Relational queries Business Intelligence as a Service Access Control Workflow Service Bus Message Queuing Live Services Live Framework for developers Live Mesh Experience Live Mesh services in next major release of Windows Live Additional data elements via Live Framework

77.  Capital Expen$e vs. Operating Expen$e  And all the financial & operational implications that entails….  Consumption-based business model  You pay only for what you use  No minimum or long term commitment  An inexpensive way to experiment  Easy to grow as your business grows  Elastic capacity and scalability  Simpler operating and management environment for developers  Integrates well with on-premises applications and services  Leverages existing technology investments and skill- sets  Hurricanes! DRP! Geo-location!

78. Register for a.NET Services account & download the SDK http://www.azure.com Download the Azure Services Training Kit and HOLs: http://www.microsoft.com/azure/trainingkit.mspx Review the PDC Content at: http://channel9.msdn.com/pdc2008

79.  Robot Pack - Lego NXT Robot Kit + WROX Robotics Developer Studio book  Mobility Pack - LifeCam NX-6000 & Wireless Notebook Laser Mouse 6000  Gamer Pack - Gears of War 2, PGR4, Mass Effect, Xbox 360 Wireless Headset & 3-month XBOX Live Card  MSDN Subscription - one-year VSTS 2008 Team Suite w/MSDN Premium Subscription  SoftLayer: Free WS 2008 Web Edition and SQL Web Edition with any server order over $179 + Giveaways will happen at the end of the last session in each breakout room. You must fill out page 1 completely and you must be present to win.

80. © 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.