Presentation given to the Wisconsin .NET Users Group on Windows Azure and SQL Azure.

1. Wisconsin .NET Users Group Sept 2009

2. Who Are We? Joseph Paradi Innovation Lead, Accenture joseph.a.paradi@accenture.com Wade Wegner Architect Evangelist, Microsoft wade.wegner@microsoft.com http://blog.wadewegner.com/

3. Cloud-Addressable Challenges Facing Today’s Enterprise 1 1 5 Infrastructure costs are fixed and ongoing, and distract from the mission of reducing business process friction Leveraging past investments to provide future value Many data centers at limit—real estate, capacity, cooling and power Matching capacity to demand Maintaining security while increasing access and transparency—within and outside the organization 2 6 Security, access, and transparency across the value chain: suppliers, partners, etc. 3 7 Lack of a common platform 4

4. And in a non-Cloud view, there are inefficiencies in addressing those issues Allocated IT-capacities Load Forecast “Under-supply“ of capacities “Waste“ of capacities Fixed cost of IT-capacities IT CAPACITY Barrier for innovations ActualLoad TIME

5. However, in a Cloud View Load Forecast Allocated IT capacities No “under-supply“ IT CAPACITY Reduction of “over-supply“ Possible reduction of IT-capacities in case of reduced load Reduction of initial investments ActualLoad Time

6. It has happened before

7. 5 key differences between legacy and cloud computing Scale Automated Service Management High Availability Multi-Tenancy Considerations Off Premises On Premises Location Homogeneous Heterogeneous Infrastructure CapEx OpEx Business model Own Lease/Rent Ownership Self Third Party Management

8. Introducing the Windows Azure platform Web and Clouds Developer Experience Third party Cloud Web applications Use existing skills and tools. Compute Storage Management Management Relational data Connectivity Access control On-premises LOB Applications Composite applications

9. Introducing Windows AzureDelivering the Reality of Cloud Computing Windows Azure delivers Cloud computing for the enterprise “It’s the transformation of our software, it’s the transformation of our strategy and our offerings across the board to fundamentally embrace services.” –Ray Ozzie Chief Software Architect Microsoft

10. Comprehensive SLAs Dependable performance Years of Microsoft Experience Faster time to market Speedier development Simpler deployment Efficiency Manage resources withless cost and effort Focus Concentrate on delivering solutions, not infrastructure Trust Rely on a solid development platform Agility Respond rapidly to changing needs Rapid monetization Scalability without complexity Fewer operational hurdles On-demand computing Elimination of idle IT capacity Lower TCO Why Windows Azure

11. NEXT UP: Windows Azure Architecture

12. From Managing Resources to Providing Abstraction BUSINESSES CONSUMERS INTERNET

13. Defining Windows Azure Architecture Fabric Fabric controller Compute Storage The Fabric Controller communicates with every server within the Fabric. It manages Windows Azure, monitors every application, decides where new applications should run – optimizing hardware utilization.

14. Windows Azure The Fabric Controller automates load balancing and computes resource scaling Security and Control Features include storage encryption, access authentication, and over-the-wire encryption using HTTPS. Industry certification is part of the Windows Azure roadmap. Computation provides application scalability. Developers can build a combination of web and worker roles. Those roles can be replicated as needed to scale the applications and computational processing power. Storage Services allow customers to scale to store large amounts of data – in any format – for any length of time, only paying for what they use or store. Geographically distributed, state-of-the-art data centers host your applications and data, internet-accessible from everywhere you choose to allow.

15. Fabric Controller Interacts with a “Fabric Agent” on each machine Monitors every VM, application and instance Performs load balancing, check pointing and recovery

16. Compute in Windows Azure GOAL: SCALABILITY Two instance types: Web Role & Worker Role Windows Azure applications are built with web role instances, worker role instances, or a combination of both. Scale out by replicating worker instances as needed. Allow applications to scale user and compute processing independently. Each instance runs on its own VM (virtual machine), replicated as needed

17. Defining the Web and Worker Roles WEB ROLE WORKER ROLE Interacts with end-user or web services Handles incoming HTTP/HTTPS requests Develop with Microsoft and non-Microsoft tools: ASP.NET, WCF, other .NET tools Java, PHP, etc. Does not accept incoming requests Initiates their own requests for data or tasks from the queue Similar to a "batch job" or Windows service

18. Storage in Windows Azure GOAL: SCALABLE, DURABLE STORAGE Tables: simply structured data, accessed using ADO.NET Data Services Queues: serially accessed messages or requests, allowing web-roles and worker-roles to interact Blobs: large, unstructured data (audio, video, etc) Windows Azure storage is an application managed by the Fabric Controller Windows Azure applications can use native storage or SQL Azure Application state is kept in storage services, so worker roles can replicate as needed

19. Blobs, Tables and Queues BLOBS: Provide a simple interface for storing named files along with file metadata QUEUES: Provide reliable storage and delivery of messages for an application TABLES: Provide structured storage. A Table is a set of entities which contain a set of properties

20. Services Management in Windows Azure GOAL: AUTOMATED APPLICATION MANAGEMENT AND CONTROL Fabric The Fabric Controller automates service management

21. Developing Applications for Windows Azure FAMILIAR DEVELOPER EXPERIENCE DESIGNED FOR INTEROPERABILITY PROVEN MICROSOFT TECHNOLOGIES Development: Visual Studio integration, offline Cloud simulation Maintenance: Local debugging, APIs for logging Management: APIs for configuration management SOAP and REST protocols XML file formats Commitment to support Java, PHP, Python and other popular programming languages Visual Studio, ASP.NET, SQL Azure integration Windows Azure integration

22. Windows Azure Skill Transfer

25. Users can choose single location or geo-distributed data centers

26. Storage data is replicated multiple times

28. Industry certification is a core part of the Windows Azure roadmap

30. HTTPS

31. Optimized for Cloud access with no admin access to guests or applications

33. NEXT UP: SQL Azure Architecture

35. Familiar relational model (DDL, DML, Indexes…)

36. Transactions

37. Ecosystem of familiar development and management tools

38. Low-friction provisioning

39. High scale

40. Multi-tenant

41. Self-management

43. Create client applications that access data in the cloud via TDS – just like on-premise SQL Server

44. Create cloud-based Web applications in Azure that use standard SQLClient libraries with ADO.NET

45. Create cloud-based REST data interfaces in Azure with ADO.NET Data Services and the Entity Framework

46. Low friction data storage provisioning

47. Web interface for simple, database provisioning

48. Scale seamlessly as needed

49. Self-managing data center

50. Automated maintenance

51. Built in high-availability and data recoverabilityREST Client SQL Client* Cloud REST (Astoria) ADO.Net +EF HTTP+REST HTTP TDS Windows Azure Web App SQL Client* Data Center TDS + TSQL Model SQL Azure * Client access enabled using TDS for ODBC, ADO.Net, OLEDB, PHP-SQL, Ruby, …

53. Architecture:

54. An Azure account provides access to SQL Azure

55. Each account can have one or more logical server

56. Implemented as multiple physical servers within a given geo-location

57. Each logical server can contain one or more logical database

58. Implemented as replicated partitioned data across multiple physical databases

59. Azure wide

61. Unit of authorization

64. Each user database is replicated to one or more servers (configurable based on SLA)

65. Client requests are routed to current “primary server” for read and write operations (based on SQL session)

66. Security, lockdown and isolation enforced in SQL tier

67. Highly scalable and state-of-the-art HA technology

68. Automatic failure detection; client request re-routed to new primary on failure

69. High SLA guarantee using logical replication (hot standby replicas)

70. Automatic management, self-healing and load balancing across shared resource pool

71. SQL Azure Database provides provisioning, metering and billing infrastructureMachine 5 Machine 6 Machine 4 SQL Instance SQL Instance SQL Instance SQL DB SQL DB SQL DB UserDB1 UserDB2 UserDB3 UserDB4 UserDB1 UserDB2 UserDB3 UserDB4 UserDB1 UserDB2 UserDB3 UserDB4 SQL Azure Database Provisioning (databases, accounts, roles, …, Metering, and Billing Scalability and Availability: Fabric, Failover, Replication, and Load balancing DBA role will change to focus on policy/logical management Scalability and Availability: Fabric, Failover, Replication, and Load balancing

73. Authenticate logins, map to users and roles

74. Authorize users and roles to SQL objects

75. Supports standard SQL logins

76. Logins are username + password strings

77. Service enforces use of SSL to secure credentials

79. ADO.NET, OLE DB, ODBC, etc.

80. Clients connect to a database directly

81. Cannot hop across DBs

82. Large surface of SQL supported within the database boundary

84. Portal and API based access

85. Ex: enumerate my servers, show server usage metrics, etc

86. Each account has one or more servers

87. Ex: srv123.data.database.windows.net

88. Each server has a virtual master database

89. Has subset of SQL Server master DB interface

90. Each server has one or more SQL logins

91. System creates sysadmin login on “server creation”

92. Databases created using “CREATE DATABASE”

93. Can be called by sysadmin or anyone with create DB permission* *

95. SQL Azure supports a subset of SQL Server patterns

96. Focus on logical and policy based administration

97. Patterns work in both SQL Azure & SQL Server

98. Enables migration of on-premise application to/from SQL Azure

99. SQL Azure Database is a multi-tenant service

100. Throttling and load balancing policies

102. Service Broker

103. Distributed Transactions

104. Distributed Query

105. Spatial

106. All server level DDL

107. All physical DDL and physical catalog views

108. Create/Alter/Drop on Database/Index/View

109. Stored Procedures (Transact-SQL)

110. Triggers

111. Constraints

112. Table variables, session temp tables (#t)

114. SQL Data Services Roadmap Internal Adoption Invitation SQL Azure CTP Commercial Availability Invitation Azure CTP MIX 2009 WWPC 2009 TechEd 2009 PDC 2009 Mar 09 May 09 Jul 09 Nov 09 Sep 09 Apr 09 Jun 09 Aug 09 Oct 09

116. We are accelerating delivery of relational database service – PDC ‘09

117. Ecosystem of tools; existing skills and knowledge

118. Majority of web and workgroup apps work as-is

119. Support for open source client libraries

120. Integration between on/off-premises: Extending SQL data platform to the cloud

121. Relational database is key capability of the Windows Azure Platform

122. Zero-friction integration with Windows Azure

123. Enables compelling scenarios on the Azure platform

124. SQL Azure design and architecture supports a wide range of scenarios

125. SQL Azure Database platform investments deliver proven value on top of SQL engine

127. NEXT UP: Pricing

129. Plans for paymentpredictability

130. Unified purchasing through EA

131. Introduction to volumediscount

132. Low barrier to entry and flexibility

133. Optimized for Cloudelasticity Windows Azure Purchasing Models

135. Load balancer programmingBlob Storage Table Storage Multiple replicas Ingress/Egress (to/from internet only) PRICE $0.12 / hour PRICE $0.15 / GB stored / month Storage transactions: $0.01 / 10k PRICE Bandwidth: $0.10 IN; $0.15 OUT; / GB

136. Windows Azure Platform Service Guarantee Storage servicewill be available/ reachable (connectivity) Your storage requests willbe processed successfully .NET Service Bus endpoint willhave external connectivity Message operation requests willbe processed successfully Serviceavailability Storage availability Database availability Role instance monitoring and restart Compute connectivity Your service is connected and reachable via web Internet facing roles will have external connectivity Database is connected to the internet gateway Availability monitoring every 5-minute interval All runningroles will be continuously monitored If role is unhealthy, we will detect and initiate corrective state Automated Systems Management >99.9% >99.95% >99.9% >99.9%

137. Windows Azure Platform Roadmap Rich Service Templates Multiple Geo Locations Multiple Languages Full Trust Active Directory and Web ID Relational & Virtualized Database Auto DB Management Simple Service Templates One Geo ASP.NET Medium Trust Automated service management Service Bus, Access Control Admin Mode/VM Deployment Geo Replication Systems Center Integration Enterprise ID Federation Distributed Queries & CLR Analytics & reporting Data Synch (DataHub) CTP Future Commercial release

138. Technology innovation Partner ecosystem Power of choice Developer Why Microsoft “IDC sees the launch of Windows Azure and Windows Azure platform as a first step in a long evolutionary path that customers will take moving them from today’s self-hosted IT to consuming a hybrid of both internally and externally hosted services, and if so desired, could eventually support a fully outsourced model.” —IDC Insight, Microsoft Unveils Cloud Services Strategy and the Windows Azure platform: Managing Customer Expectations and Competitive Pressures as Solution Evolves Is Key, Nov 2008, Doc #215034

139. NEXT STEPS Sign up for Windows Azure and SQL Azure: http://www.windowsazure.com http://msdn.microsoft.com/en-us/sqlserver/dataservices/ Take a look at: Windows Azure & SQL Azure access Developer tools White papers Sample applications