Wisconsin .NET UG - Windows Azure
Download as PPTX, PDF0 likes1,610 views
The document summarizes a presentation given by the Wisconsin .NET Users Group in September 2009. It discusses challenges facing enterprises and how cloud computing addresses issues like high infrastructure costs, limited data center capacity, and lack of a common platform. It introduces the Windows Azure platform and how it provides automated management, scalability, and a familiar development experience. Key aspects of Windows Azure including its architecture, SQL Azure, and pricing models are summarized.
Wisconsin .NET UG - Windows Azure
- 1. Wisconsin .NET Users GroupSept 2009
- 2. Who Are We?Joseph ParadiInnovation Lead, Accenturejoseph.a.paradi@accenture.comWade WegnerArchitect Evangelist, Microsoftwade.wegner@microsoft.comhttp://blog.wadewegner.com/
- 3. Cloud-Addressable ChallengesFacing Today’s Enterprise115Infrastructure costs are fixed and ongoing, and distract from the mission of reducing business process frictionLeveraging past investments to provide future valueMany data centers at limit—real estate, capacity, cooling and powerMatching capacity to demandMaintaining security while increasing access and transparency—within and outside the organization26Security, access, and transparency across the value chain: suppliers, partners, etc.37Lack of a common platform4
- 4. And in a non-Cloud view, there are inefficiencies in addressing those issuesAllocated IT-capacitiesLoad Forecast“Under-supply“ of capacities“Waste“ of capacitiesFixed cost of IT-capacitiesIT CAPACITYBarrier forinnovationsActualLoadTIME
- 5. However, in a Cloud ViewLoad ForecastAllocated IT capacitiesNo “under-supply“IT CAPACITYReduction of “over-supply“Possible reduction of IT-capacities in case of reduced loadReduction of initial investmentsActualLoadTime
- 6. It has happened before
- 7. 5 key differences between legacy and cloud computingScaleAutomated Service ManagementHigh AvailabilityMulti-TenancyConsiderationsOff PremisesOn PremisesLocationHomogeneousHeterogeneousInfrastructureCapExOpExBusiness modelOwnLease/RentOwnershipSelfThird PartyManagement
- 8. Introducing the Windows Azure platformWeb and CloudsDeveloper ExperienceThird party CloudWeb applicationsUse existing skills and tools.ComputeStorageManagementManagementRelational dataConnectivityAccess controlOn-premisesLOB ApplicationsComposite applications
- 9. Introducing Windows AzureDelivering the Reality of Cloud ComputingWindows 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 SLAsDependable performanceYears of Microsoft ExperienceFaster time to marketSpeedier developmentSimpler deploymentEfficiencyManage resources withless cost and effortFocusConcentrate on delivering solutions, not infrastructureTrustRely on a solid development platformAgilityRespond rapidly to changing needsRapid monetization Scalability without complexity Fewer operational hurdlesOn-demand computingElimination of idle IT capacityLower TCO Why Windows Azure
- 11. NEXT UP:Windows Azure Architecture
- 12. From Managing Resources to Providing AbstractionBUSINESSESCONSUMERSINTERNET
- 13. Defining Windows Azure ArchitectureFabricFabric controllerComputeStorageThe 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 AzureThe Fabric Controller automates load balancing and computes resource scalingSecurity 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 ControllerInteracts with a “Fabric Agent” on each machineMonitors every VM, application and instancePerforms load balancing, check pointing and recovery
- 16. Compute in Windows AzureGOAL:SCALABILITYTwo instance types: Web Role & Worker RoleWindows 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 RolesWEB ROLEWORKER ROLEInteracts with end-useror web servicesHandles incomingHTTP/HTTPS requestsDevelop with Microsoft andnon-Microsoft tools:ASP.NET, WCF, other .NET toolsJava, PHP, etc.Does not acceptincoming requestsInitiates their own requestsfor data or tasks from the queueSimilar to a "batch job"or Windows service
- 18. Storage in Windows AzureGOAL:SCALABLE, DURABLE STORAGETables: simply structured data, accessed using ADO.NET Data ServicesQueues: serially accessed messages or requests, allowing web-roles and worker-roles to interactBlobs: large, unstructured data (audio, video, etc)Windows Azure storage is an application managed by the Fabric ControllerWindows Azure applications can use native storage or SQL AzureApplication state is kept in storage services, so worker roles can replicate as needed
- 19. Blobs, Tables and QueuesBLOBS: Provide a simple interface for storing named files along with file metadataQUEUES: Provide reliable storage and delivery of messages for an applicationTABLES: Provide structured storage. A Table is a set of entities which contain a set of properties
- 20. Services Management in Windows AzureGOAL:AUTOMATED APPLICATION MANAGEMENT AND CONTROLFabricThe Fabric Controller automates service management
- 21. Developing Applications for Windows AzureFAMILIAR DEVELOPER EXPERIENCEDESIGNED FOR INTEROPERABILITYPROVEN MICROSOFT TECHNOLOGIESDevelopment: Visual Studio integration, offline Cloud simulationMaintenance: Local debugging, APIs for loggingManagement: APIs for configuration managementSOAP and REST protocols XML file formatsCommitment to support Java, PHP, Python and other popular programming languagesVisual Studio, ASP.NET, SQL Azure integrationWindows Azure integration
- 22. Windows Azure Skill Transfer
- 23. Providing Security with Windows AzurePHYSICAL:Microsoft data centers with modern and current security processes
- 24. Redundant power supplies from separate providers, battery and diesel backup generators, climate control, and fire prevention and suppressionCONTINUITY: Multiple data centers in different geographies
- 25. Users can choose single location or geo-distributed data centers
- 26. Storage data is replicated multiple times
- 27. Fabric is designed to be backed up and restored from checkpointsCOMPLIANCE & CERTIFICATION:Microsoft is committed to complying with all local laws
- 28. Industry certification is a core part of the Windows Azure roadmap
- 29. Customers are ultimately responsible for the security and compliance of their services or applications–Windows Azure is a platformLOGICAL:Storage encryption and authentication
- 30. HTTPS
- 31. Optimized for Cloud access with no admin access to guests or applications
- 32. Applications and users not allowed to update the underlying environmentBuilding Solutions with the Windows Azure PlatformSQL Azure: Scalable, relational, Cloud-enabled database services.NET Services: Framework for access control and communication between Cloud-aware applications
- 33. NEXT UP:SQL Azure Architecture
- 34. Benefits of SQL Azure databaseSQL Azure Database delivers the value of hosted relational database with the differentiated benefits of a managed database as a utilityHosted RDBMSManaged RDBMSSQL query processor
- 35. Familiar relational model (DDL, DML, Indexes…)
- 36. Transactions
- 37. Ecosystem of familiar development and management tools
- 39. High scale
- 40. Multi-tenant
- 41. Self-management
- 42. Automatic HA and DRSQL Azure Database Product Architecture overviewSQL Azure Database combines the bestof simple storage and hosted RDBMSBrowserApplicationApplicationApplicationODBC, OLEDB, ADO.Net PHP, Ruby, …Flexible access to data in the cloud
- 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
- 51. Built in high-availability and data recoverabilityREST ClientSQL Client*CloudREST (Astoria)ADO.Net +EFHTTP+RESTHTTPTDSWindows AzureWeb AppSQL Client*Data CenterTDS + TSQL ModelSQL Azure* Client access enabled using TDS for ODBC, ADO.Net, OLEDB, PHP-SQL, Ruby, …
- 52. Data Platform DesignAccountGoal: A storage platform built for extreme scale and low cost
- 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
- 60. Billing instrumentHas one or moreServerDatabase metadata
- 62. Unit of geo-locationHas one or moreDatabaseUnit of consistency
- 63. Contains Users, Tables, Views, etc…Logical User DatabasesUses shared infrastructure at SQL database and below
- 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 5Machine 6Machine 4SQL InstanceSQL InstanceSQL InstanceSQL DBSQL DBSQL DBUserDB1UserDB2UserDB3UserDB4UserDB1UserDB2UserDB3UserDB4UserDB1UserDB2UserDB3UserDB4SQL Azure Database Provisioning (databases, accounts, roles, …, Metering, and BillingScalability and Availability: Fabric, Failover, Replication, and Load balancingDBA role will change to focus on policy/logical managementScalability and Availability: Fabric, Failover, Replication, and Load balancing
- 72. Security and Connection ModelsSecurityUses regular SQL security model
- 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
- 78. Future support for AD Federation, WLID, etc as alternate authentication protocolsConnectionsConnect using common client libraries
- 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
- 83. Future work will relax many of these constraintsProvisioning ModelAccount and server provisioning
- 84. Portal and API based access
- 85. Ex: enumerate my servers, show server usage metrics, etc
- 86. Each account has one or more servers
- 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**
- 94. Compatibility with SQL ServerSQL Server has many patterns for accomplishing tasks
- 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
- 101. Examples: limit on DB size, duration of transaction, …V1 Goal: Address the needs of 95% or more web and departmental applicationsIn Scope for v1Out of Scope for v1CLR
- 102. Service Broker
- 104. Distributed Query
- 105. Spatial
- 106. All server level DDL
- 107. All physical DDL and physical catalog views
- 110. Triggers
- 111. Constraints
- 112. Table variables, session temp tables (#t)
- 113. + lots of othersSQL Azure Database Customer ScenariosDepartmental ApplicationsWeb ApplicationsDepartmental workgroup applications with low concurrency and cyclical usage patternsSmall customers or start ups with Web applications of all scale that have simple RDBMS needsData HubsISV/SaaS OfferingsSecure data hubs that consolidate multiple data sources and enable access from multiple locations and devicesTraditional ISVs extending offering or selling software hosted in the cloud (including SaaS ISVs)
- 114. SQL Data Services RoadmapInternal AdoptionInvitation SQL Azure CTP Commercial AvailabilityInvitation Azure CTP MIX 2009WWPC 2009TechEd 2009PDC2009Mar 09May 09Jul 09Nov 09Sep 09Apr 09Jun 09Aug 09Oct 09
- 115. Key TakeawaysSQL Azure Database is real and in production with Microsoft enterprise services
- 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
- 126. From very cheap and highly-consolidated to still inexpensive and highly-isolatedSoftware + Services Architecture“When you combine the ever-growing power of devices and the increasing ubiquity of the Web, you come up with a sum that is greater than its parts.” —RAY OZZIETHREE CORE PRINCIPLES:Experiences should span beyond a single deviceInfrastructure and solutions should extend from the server to the CloudTightly coupled systems should give way to federations of cooperating systems and loosely coupled compositions
- 127. NEXT UP:Pricing
- 128. ConsumptionSubscriptionVolume licensing“Value for a commitment”“Coordinated purchasing”“Pay as you go and grow”Planned for post PDCSelect offers at PDCAvailable at PDC launchDiscounts for commitment
- 130. Unified purchasing through EA
- 132. Low barrier to entry and flexibility
- 133. Optimized for Cloudelasticity Windows Azure Purchasing Models
- 134. Windows Azure Pricing MetersCOMPUTESTORAGEBANDWIDTHVirtual Machine instancesLoad balancers, routers, etc.Relational DB instancesAutomated service management Fabric controller operations (deploy/upgrade/delete/scale)
- 135. Load balancer programmingBlob StorageTable StorageMultiple replicasIngress/Egress (to/from internet only)PRICE$0.12 / hourPRICE$0.15 / GB stored / monthStorage transactions: $0.01 / 10kPRICEBandwidth: $0.10 IN; $0.15 OUT; / GB
- 136. Windows Azure Platform Service GuaranteeStorage servicewill be available/ reachable (connectivity)Your storage requests willbe processed successfully.NET Service Bus endpoint willhave external connectivityMessage operation requests willbe processed successfullyServiceavailabilityStorage availabilityDatabase availabilityRole instance monitoring and restartCompute connectivityYour service is connected and reachable via webInternet facing roles will have external connectivityDatabase is connected to the internet gateway Availability monitoring every 5-minute intervalAll runningroles will be continuously monitoredIf role is unhealthy, we will detect and initiate corrective stateAutomated Systems Management>99.9%>99.95%>99.9%>99.9%
- 137. Windows Azure Platform RoadmapRich Service TemplatesMultiple Geo LocationsMultiple LanguagesFull TrustActive Directory and Web IDRelational & Virtualized Database Auto DB ManagementSimple Service TemplatesOne GeoASP.NETMedium TrustAutomated service managementService Bus, Access ControlAdmin Mode/VM DeploymentGeo ReplicationSystems Center IntegrationEnterprise ID FederationDistributed Queries & CLRAnalytics & reportingData Synch (DataHub)CTPFutureCommercial release
- 138. TechnologyinnovationPartnerecosystemPowerof choiceDeveloperWhy 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 STEPSSign 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 accessDeveloper tools White papersSample applications