Recommandé
Contenu connexe
Similaire à 1.Ms 云计算平台介绍
Similaire à 1.Ms 云计算平台介绍 (20)
Dernier
Dernier (20)
1.Ms 云计算平台介绍
- 1. Azure Services 杨刚 Technical Manager 万锐信息技术服务有限公司 Email: Gyang@Winarray.com MSN: YG2008@GMail.com 1
- 2. 为什么要使用Cloud? Azure Services 平台 Tour of the services SDKs 和 可用服务 路线图 Q&A 2
- 3. Platform Server • 托管软件平台 Client Mobile Cloud • 共享的架构 • 虚拟化 和 不断变化 • 更高的服务级别 • 按使用支付模型 3
- 4. Why a Cloud Platform? 软件经济模式正在改变 减少投资和运营成本 简化应用的部署和管理 应用和基础设施更加灵活 成本效益最大化 关注于新功能而不是基础设施
- 6. Azure Services Platform 简化业务场景 服务托管在微软的数据中心 面向高可用性和可扩展性进行设计 支持多种协议包括HTTP, REST, SOAP, AtomPub 基于Azure Service进行连接 熟悉的工具，语言 & frameworks with .NET & Visual Studio 提供 on-premises, cloud 或 hybrid solutions 多种选择 与现有系统进行集成，例如：AD 6
- 7. 正在运营的扩展服务 30B Live ID authentications/month 2B Live Search queries/month 10B MSN page views/month 240B Messenger messages/month 微软的构建来运营您的服务 典范, WA: Complete, approx 500K sq ft San Antonio, TX: Opening Fall 08, approx 475K sq ft Chicago, IL: Opening Spring/Summer 09, approx 550K sq ft Dublin, Ireland: Opening Summer 09, approx 570K sq ft Des Moines, Iowa: Recently announced land purchase
- 9. Windows Azure Windows Cloud : Windows : : 9
- 11. Windows Azure 11
- 12. Demo: Hello Windows Azure 我们看到的 Azure 所提供的… Simple ASP.NET app Environment to run code Visual Studio 2008 SP1 Machines, rack space, switches, connecti Roles & instances are vity models in config Automated deployment Local F5 debugging & configuration Azure Services Portal Isolation, redundancy, lo Deployed to the cloud ad balancing Switched from staging to Abstraction & Flexibility production 12
- 13. SQL Services 扩展SQL Server 数据平台到 Cloud Data Reference ETL Reporting Mining Data Data Warehouse Database: Data Sync: Reporting: & Data Mining: ETL: Reference Data: 13
- 14. .NET Services 扩展.NET基于互联网的扩展公用服务到 cloud Service Bus: Access Control: Workflow Service: 14
- 15. .NET Services .NET Service Bus Service Service Application .NET Workflow Service Service http://service./ Application .NET Access Control Service Service Workflow SDS Authority Application 15
- 16. SQL Services & .NET Services 16
- 17. Hello Azure Services : Azure Services SQL Data Services (SOAP) http://data.database.windows.net ASP.NET Web Site (REST) .NET Service Bus http://servicebus.windows.net/... http://...cloudapps.net (Running in Windows Azure) .NET Access Control Service Manufacturer Service (Running on-premises) 17
- 18. Live Services 以用户为中的服务，提供访问Windows Live和用户数据的编 程方式 Live Framework 18
- 19. ? Access user data Access information on user devices Access user’s Share user’s data social graph Access Sync user’s data user’s profile Provide news Manage on actions applications Provide access control to user’s data 19
- 20. Live Framework Mesh-enabled Web应用 托管和部署在用户的 Mesh 运行桌面在Live Desktop 充分利用Live Services Live Framework-enabled Web Site Web apps可以连接用户数据 Web Site 必须明确代理方式 GET https://user-ctp.windows.net/v0.1 20
- 21. Azure •Developer CTP for • Additional features & CTPs Services, SDKs, and Tools • Plans for pricing & SLAs • Additional Data Centers Today H1 2009 Based on customer Feedback during CTPs 21
- 22. 三种不同类型的邀请代码: 1. Windows Azure 2. .NET & SQL Services invitation code 3. Live Framework & Services invitation code 如何得到? Go to http://www.azure.com Submit a request for an invitation code You will receive invitation codes for .NET Services, SQL Services, and Live Services during the labs. 22
- 23. SDKs & Tools November CTP SDKs & Visual Studio Tools SQL Services SDK Live Framework SDK Visual Studio Tools for Live Framework Java & Ruby SDKs for .NET Services December CTP SDK .NET Services SDK January CTP Windows Azure SDK Visual Studio Tools for Windows Azure 23
- 24. Azure 1. 综合cloud 服务平台 2. 帮我们从基础设置中抽离 3. 灵活的混合并匹配服务 4. 连接on-premises 环境 5. 熟悉的编程模型和工具 6. Live Services 提供富客户端体验 7. 标准协议和编码格式 (HTTP, REST, ...) 24
- 25. 25
- 26. Azure Services Training Kit Hands-on labs available in an installable package http://www.azure.com Azure Services Management Tools / Sample PowerShell CmdLets and MMC console for managing SQL Data Services, Workflow Services, and Access Control http://code.msdn.microsoft.com/AzureManagementTools
- 27. © 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. 27
Notes de l'éditeur
- Slide objectives: Welcome & introductionsSpeaking Points: THANK YOU! – First, I want to thank you for investing your time to learn about the Azure Services Platform. We do not take it lightly when we have partners and customers take their time to learn about our new technologies. I hope that this is an informative and beneficial event. Notes:
- Demo: Hello Windows AzureThe step-by-step demo script for this demo is included in the Azure Services Training Kit.
- Slide objectives: Summarize what the audience just saw with the Hello Windows Azure demo.Speaking Points: What you sawSo we just saw a number of things within this simple demo.First you saw a simple ASP.NET web application, like many of you have built before.We created the application using Visual Studio 2008 SP1, the existing tools that we are already familiar with.We were able to model the roles and instances for our Windows Azure application in a simple config file.You saw how the Windows Azure development fabric provides a local environment for developing, debugging, and testing our applications – which is integrated directly with Visual Studio. Finally, you saw how we could deploy our applications to Windows Azure running in the cloud and in a matter of minutes have the application running in the cloud and switch from staging to production.What Azure ProvidedWhat is more exciting then this simple application is what you didn’t see, but what Windows Azure provided.First, Windows Azure provided an environment to run code – to run our ASP.NET application.It provided all of the infrastructure such as machines, rack space, connectivity, and switches.It also automated and simplified the deployment and configuration. At no point did we have to remote into machines or FTP files or synchronize our application across machines. This automated service management was provided by Windows Azure.Windows Azure also provided isolation for us – where our application is isolated from other apps that either we would develop or other organizations would develop. We also saw how by simply specifying the number of instances in the service model, Windows Azure delivered key capabilities such as redundancy and load balancing for our application.Ultimately, what this results in is abstraction and flexiblity.Notes:
- Slide objectives:Define SQL Services and enumerate the current and future services.Speaking Points: Question: How many of you use SQL Server today?Imagine having SQL Server functionality ranging from SQL Server databases, to reporting, analytics, and integration services and having that functionality available to you in the cloud – without having to deploy and configure clusters and manage and operate a SQL environment.That is what we want to accomplish with SQL Services. We are extending the SQL Server Data Platform to the cloud.This will happen over several releases of the Azure Services Platform. In the short term, we are focusing on two key services. SQL Data Services and Data Sync.SQL Data ServicesAt the Mix conference in 2008 we first announced SQL Data Services. SQL Data Services is designed to provide data storage and query capability in the cloud. Today with SQL Data Services, we are exposing data through SOAP and REST based programming models and we are just starting to surface the underlying database capabilities such as joins. Over time we will continue to provide more relational support that is familiar to developers using SQL Server.Data SyncWe are also supporting data synchronization, so you can easily synchronize data to or from the cloud using the Sync framework. If you’re not familiar with the sync framework, it is an extension to the .NET Framework 3.5 that provides an extensible engine for synchronization across a variety of data sources.Future servicesThe grey boxes that you see here represent future services or capabilities that will be added to SQL Services in future versions of SQL Services. For example, one of the common areas of feedback we have heard from partners and customers is the desire to perform data transformations and processing in the cloud. We have also heard requests for reporting and analysis services in the cloud – much like SQL Server developers are familiar with today.Notes: Databases are crucial to business applications, and really crucial to all applications that are being built today. And so what we're doing is we've taken and built a scale-out implementation of SQL Server that we're making available through something we call SQL Services. SQL Services is built on SQL Server. It's SQL Server underneath it. And over time, what we will do is provide more and more of the capabilities that you're familiar with in on-premises SQL Server into the SQL Services.And so today we have a SQL data services environment that lets you build a database built on entities. Over time, we'll grow those capabilities in the relational space. We will, in the future, be providing capabilities like data synchronization to allow you to synchronize on-premises information as well as information on mobile workers with the cloud services to be able to synchronize that data, data mining services and analysis services to be able to dig in and understand what's happening at a detailed level, things eventually like geospatial and a whole broad set of things we'll be bringing available to this environment. The basic goal here is that with the cloud environment, you need a database just like you needed one on premises, and in fact, we're providing that set of scale-out services as a part of the Azure Services Platform.
- Slide objectives: Define and enumerate the .NET Services.Emphasis that we are using the Windows Communication Foundation and Windows Workflow Foundation as programming models for .NET Services.Speaking points: Much in the same way that SQL Services is about extending SQL Server to the cloud, we are also extending key .NET capabilities to the cloud as services.We call these .NET Services. Some of you maybe familiar with previous codenames such as BizTalk Services.These services are really key components you would need for building distributed, connected applications. When we talk about connecting to your existing on-premises applications and enabling the composition of hybrid (Cloud + on-premises) applications – that is where .NET Services really comes in.There are currently three .NET Services: the Service Bus, the Access Control Service, and the Workflow ServiceService Bus:The Service Bus is designed to provide a general purpose application bus, available on the internet at internet scale. You can really thin of the Service Bus as being similar to an Enterprise Service Bus that many enterprise organizations have today. However, we believe that when providing a Service Bus as a programmable service on the internet, there are a wider range of scenarios for many more types of organizations.Fundamentally, the .NET Service Bus is about connecting applications across network and application boundaries and making key message exchange patterns such as publish and subscribe messaging very simple.Access Control:The Access Control service is designed to provide rules-driven, claims-based access control for applications. Essentially, this allows you to define authorization rules for your applications using the claims-based approach that we are adopting within many Microsoft products and technologies and that is becoming adopted in the industry.Workflow Service:The workflow service provides a shared execution environment for running declarative workflows. These workflows are really focused on orchestrating messages across the service bus.So you can imagine the scenario where you might need to publish a few messages on the bus and wait for responses. We want to enable you to model these patterns declaratively and execute these orchestrations in the cloud.In the case of all of these services, we are extending the programming models and tools that are available in the .NET Framework today. Specifically, the Service Bus is delivered as a set of extensions to WCF – in the form of new bindings that you can configure. The Workflow Service, as another example, uses Windows Workflow Foundation and the WF designer built into Visual Studio to design the workflows that interact with the service bus.Notes: Windows Azure has the .NET Framework built into it so thatyou can use those services within your application.But just like your application must be designed to scale out, the services that we have built into Windows over time in .NET also need to be designed and built in a way that can scale out naturally. We want to create services for you, and that's the purpose of .NET services, creating a pool of resources available to you to take advantage of and do things within your application very simply. So we're including a built-in, scale-out implementation of a service bus. The service bus lets you connect your on-premises systems securely into the cloud, into the Azure environment, while allowing your data and your information to traverse firewalls, solving a problem that is a bane of many application developments. Access control is a key thing, the need to have federated access, federated identity providers, identity authorities that exist in a heterogeneous way. Many enterprises have their own identity provider, many of them are Active Directory, there are other key identity providers out there. Access control provides a way of enabling federation across these different identity providers both on premises and then into the cloud. Work flow is a key mechanism used by many applications. Having work flow that scales out across hundreds of servers to meet the needs, the demanding needs of demanding business applications is critical, and what we've done is we've taken the .NET work flow services that are so familiar to you on the on-premises Windows systems, and taken those same services and put them into the cloud in Windows Azure and .NET services to allow you to write work flows that span from the on-premises system into the cloud environment.
- Slide objectives: Explain the different services provided by .NET Services and illustrate how they could be used.Speaking points: So we just talked about the .NET Services, here you can quickly see the role they play in applications..NET Service Bus:Again, the .NET Service Bus provides the connectivity between network and application boundaries to enable an application to communicate with multiple services. The Service Bus runs in the cloud and you connect to it from your applications – regardless of where you applications or the services you are connecting to are running.In this way, the Service Bus can really abstract you from where the services are running. Over time we will add more support to the service bus including rich discovery support and queuing..NET Workflow Service:As you can see here, the workflow service is really about orchestrating communications with other services.These could be services provided by the Azure Services Platform, or services that you might create yourself.Access Control ServiceFinally, the Access Control Service is designed to transform incoming claims into outgoing claims based on rules you define. These claims can then be used to define the authorization requirements for access services – such as your custom services connected to the service bus or other services provided by the Azure Services Platform.Notes:
- Demo: Hello Azure ServicesThe step-by-step demo script for this demo is included in the Azure Services Training Kit.
- Slide objectives: Explain how the demo scenario composed services from the Microsoft Services Platform. Speaking points: So we’ve seen a lot of services, let’s spend a couple minutes reviewing the architecture of our Hello Azure Services example. First, we have an ASP.NET Web site. That web site is running in Windows AzureNotes:
- Slide objectives: Explain how the demo scenario composed services from the Microsoft Services Platform. Speaking points: Live ServicesLive Services are user-centric services that are designed to provide programmatic access to a user’s data and Windows LiveAnother definition: Live Services are a set of build blocks for handling user data and application resources which can connect your application to hundreds of millions of users.Live Services are important both as part of the Azure Services Platform. They are unique compared to the general purpose services such as .NET Services and SQL Services. Live Services are about both the client and the cloud. Live Services are designed to bring together the client and the cloud with an end user experience that helps users connect their data, their people, the applications, and their devicesEnable developers to create applications that connect data, devices, people and applications.Existing Live ServicesToday, you may or may not no this, but Microsoft runs some very high scale live services today. Microsoft has had several Live Services available for a few years now.For instance, our Identity Service (Live ID) has been used for several years and today is serving up 1.2B authentications per day. With Live ID we have a massive credential database where users can use their username and password to log onto any Web site, Microsoft or external, that supports Live ID. Live Spaces provides storage for user data today. Live Messenger provides communication and presence capabilities as well as contact management. Today there are 460M contact entries of which there are 30 billion relationships defined in Live Messenger – for instance people specify who they friends are, etc.Finally, Virtual Earth provide rich mapping and location information. Virtual Earth is being used by…Live meshIn March at the Web 2.0 conference Microsoft announced Live Mesh.Live Mesh was initially introduced as an application that end users can install to synchronize files and folders. Live Mesh also provides a number of underlying services. We are now exposing these services for developers to consume as part of their applications.New Live ServicesSome of these new Live Services include:User Management: Provides the ability to manage a list of users, relationship between users, and permissions for the users.Device Management: Provides the ability to manage a user’s multiple devices from Windows desktops, to mobile devices, and Macs. Seamless experience across devicesApplication Management: Provides the ability to install and configure applications across multiple devices. These applications, which you’ll see in a few minutes, can run online or offline.Data Synchronization: Finally, there is a data synchronization service that is designed to synchronize user-centric data across multiple devices and from the client to the cloud. For users this will provide access to data where ever you are and what ever device.These are all now services that can be used as part of your applications – whether they are web applications, applications that run in the Live Mesh environment, or applications that are fully installed on your machines. The Live Framework One thing that is pretty challenging today is that some of these services exist, but their in their own silos. They have different APIs, different ways to authenticate, etc. Live Framework provides a uniform way to program against the wide range of Live Services from any platform, programming language, application or device. There are two primary components of the Live Framework:A common programming model that consists of client libraries for .NET, Silverlight, and Javascript.Live Operating Environment that provides local running instances of Live Services with support for synchronization. This enables applications to use the Live Services both online and offline.Talk to client the same way you talk to cloudFinally, the Live Services and Live Framework is designed to be open and interopable – by providing support for standard protocols and formats such as HTTP, XML, ATOM, RSS etc.Live Mesh provides a client experience on top of the Live framework and services. It installs the Live Framework. Notes: We've had the Live Services available for some time. Some of the key components of Live Services include our identity functionality. With Live ID we have a massive credential database where users can use username, password to log onto any Web site, Microsoft or external, that supports Live ID. This is a great value proposition for users because you don't have to remember as many usernames and passwords, you don't have to remember as many usernames and passwords, you don't have to have a different one for each Web site. It also enables you to be more robust in your management of those credentials, changing your password more often, for example.We've also had the capability for developers at third party Web sites to make use of Live ID, which is a value proposition for the Web site because it reduces the registration hassle for creating a new account on that Web site, and also allows users not to have to remember yet another username and password for that Web site. We have had lots of feedback from customers about wanting to customize that logon experience, so that it's consistent with the look and feel of their Web site. That's one of the features that we're talking about with Live ID, the customization of that sign-in experience.Also we've heard loud and clear from our customers that people really want federation capabilities of Live ID. We’ve talked about the Microsoft Services Connector and the Microsoft Federation Gateway, which enabled businesses and ISVs to connect with Live Services in a way that they retain control of the accounts that the users use, so you don't have to have everything in Live ID. The account control is in Active Directory in a way that the administrator of that site still retains control of it. And finally you heard yesterday our announcements about Live ID as an Open ID provider. We've heard loud and clear from customers that Open ID is important to them, and we want our customers to be able to use their Live ID credentials from any Web site that supports Open ID.Next with our directory functionality we have an enormous social graph that users have created in Windows Live Messenger and Windows Live Hotmail. With the contacts API we've made it possible for developers to create experiences where you can leverage that social graph, make a more compelling experience for your users, and even help with things like viral adoption of your experiences.With communication and presence we have capabilities for developers to enhance their Web sites with instant messaging functionality. The Windows Live Messenger client libraries, the IM controls enable you to integrate Windows Live Messenger experiences with your Web site in a way that makes sense for that site.And finally, we have the search and geospatial capabilities that allow developers to include those in their experiences as they see fit.All this is done in a way that we've tried to make very easily integrateable with your experiences, and we do it based on standards based interoperable protocols, so that you can make use of these services without having to have the whole Microsoft stack. Of course, you'll have great access from .NET or other Microsoft infrastructure, but additionally because it's based on standard protocols like HEC, REST, SOAP, etc., you can invoke these services from any developer stack.
- Slide objectives: Highlight a few of the scenarios that developers can address with Live Services and the Live Framework.Emphasis that these are user-centric capabilities. Speaking points: There are a number of scenarios for using Live Services and the Live Framework. For example, you can use these technologies to access information on a user’s devices – when they provide delegated access, or what we call delegated authorization. This data might be files and folders, but it might also be their contacts or other personal data such as their holiday shopping list.We could also access a user’s profile and provide them a more seamless web experience.We could deliver applications to users that they could run on the web or locally on their machines – even offline.We can synchronize a user’s data across multiple devices and enable them to share it with other users.So there are a wide variety of scenarios. These are just a few examples. However, there is one common theme here – these are all user-centric scenarios. They involve participate from the end user and often involve connecting with client-side software components (Live Mesh) to provide these seamless experiences.Notes:
- Slide objectives: Explain the different types of Live Framework applications that are surfaced in the Azure Services Developer portal.Speaking points: So as I mentioned, over time the Live Framework becomes the common way to program against the live services…Today, with the current CTP, there are two general types of applications that you can build with the Live Framework and Live Services.The first application type is a Mesh-enabled Web Application. A MEWA is an application that is developed using client web technologies such as HTML, CSS, and javascript or with rich technologies such as Silverlight. MEWAs can be installed by end users and they run either on the web as part of a user’s Live Desktop or locally on a user’s machine.The key benefit of MEWAs is that they can also run offline and take advantage of live services to seamlessly synchronize data between a user’s devices and the cloud.MEWAs can also take advantage of other live service capabilities such as device management, user and membership information, and the extensible data or resource model.The second application type is a Live Framework-enabled Web site. A Live Framework-enabled web site is essentially a web site that can work with a user’s data because the user has explicitly granted the web site access to their data.As I mentioned earlier, this process is referred to as delegated authorization.One good example is imagine going to an online auction site and granting that auction site the ability to view your wish list of items and publish new items into your wish list – then imagine taking that wish list offline and having it synchornized across multiple devices.Notes:
- Slide objectives: Explain the agenda and set expectations about what attendees will learn about in this presentation.Speaking Points: For the next 75 minutes in this session, you will learn about Microsoft’s Cloud Services initiatives and receive a very quick tour of the Azure Services Platform. The objective for this session is to help you understand what Azure is, how to use it, how to get started, and how to dig deeper.Polling questions: By a show of hands, how many of you heard about the Azure announcements made at the Microsoft Professional Developers Conference in October? How many of you would consider yourselves ISVs? Enterprise organizations? Small/medium businesses? System Integrators? Other?You have no doubt heard a lot of noise about “Cloud Computing”, “Utility Computing”, and “Cloud Services”. Before diving into the details about Azure, we will first talk about what is happening in the industry around the cloud. We will then define the Azure Services Platform and discuss some of the individual services that make up the platform.I will summarize the SDKs and service availabilityFinally, I will share the high-level roadmap and we will have some time for Q&A. Scope:This is a overview level session. I will show some brief demos and some code, but we will spend most of the time defining the Azure Services Platform and giving you an overview of the services through slides. I will intentionally show you simple demos to help you understand the concepts for the services and how they can be used. We will dive much deeper in the following sessions.Notes:
- Slide objectives: Bring clarity to the invitation codes and access tokens. Call out the specific tokens that the attendees will get during the training workshopSpeaking points: Question: How many of you already have your tokens?With the current Customer Technology Previews, we are providing free access to the Azure Services Platform for developers to begin prototyping applications. The invitation tokens are a way for us to manage the free access to the resources.There has been quite a bit of confusion about the invitation codes. There are three different types of invitation tokens available. As part of this training workshop, you will get access tokens for .NET Services, SQL Services, and Live Services. Your colleagues can also submit requests for tokens at the www.azure.com web site. We are clearing out the queue ASAP and most requests are fulfilled in 24 hours.
- Slide objectives: Bring clarity to the different types of SDKs and Tools available. Speaking points: There are several SDKs and Visual Studio extensions available for the Azure Services. This slide lists all of the current Customer Technology Preview SDKs and ToolsWe will continue to release updates in the coming months. It is important to understand that you only need the SDKs and Tools for the services you are targeting and in some cases the SDKs and Tools are completely optional. Finally, the machines you will use for the labs have been fully configured with these SDKs and Tools. Notes:
- Slide objectives: Summarize the top 7 takeaways for the Azure Services Platform. These are the key value propositions for developers.Speaking points: Comprehensive cloud services platformCloud computing, general purpose, & user-centricAbstraction, flexibility, and choiceAbstracts infrastructure, machines, and connectivityMix & match services as neededConnectivity to on-premises products Familiar programming model & tools Apply your .NET & Visual Studio skills to the cloudRich client experiences with Live ServicesStandard protocols & formats (HTTP, REST, ATOM, ...)Community-based libraries & samplesInterop with multiple platformsNotes:
- Slide objective:Address the “Why” question up front. Why are we investing in services.Motivate the need for the services platform Frame the challenges with building applications today Speaking Points:Before talking about the cloud, I think it’s important to reflect on where we’re at in the industry. Today there are a number of options you have when building applications. There are three types of platforms established in the industry:Client - Rich client applicationsServer - I suspect many of you are building server-based applications today, ranging from web applications to web services.Mobile - Virtually all of you have a mobile device.Shift to Cloud ComputingToday there is a shift emerging that we believe will eventually effect virtually every type of organization from small start-ups to large enterprises. This industry shift is the use of cloud computing and cloud services. Some have referred to this shift as disruptive. We are starting to see organizations extend compute, storage, and other workloads to the cloud – where these workloads will be operated and managed by a software vendor. Some organizations are using the cloud for temporary compute power, as is the case with the New York Times, who needed compute resources to convert their archived library of articles to PDFs – some are more permanent such as data archival. We believe that this shift represents the emergence for a fourth type of platform – the cloud.There are a few unique characteristics about a cloud platform.First, is a hosted software platform using shared infrastructure – where another organization is providing the infrastructure. Designed to be virtualized and dynamic – to achieve economic benefits and provide flexibility. A cloud platform must be much more than just hosting code. We believe that a cloud platform must deliver higher level services that enable the development and deployment of applications. Finally, a key characteristic is that a cloud platform must provide a pay as you go pricing model. The pricing model must be as flexible as the platform. Notes:
- Slide objectives: Frame the problems with applications today and the reasons for Cloud Computing / Services.Speaking Points: Some of you maybe asking why? Why do we need a new type of platform? So what makes the cloud attractive to organizations?Problems today:Many of the challenges with building applications today have very little to do with development tools, programming languages, or frameworks. Rather, many of the challenges that organizations face are related to the infrastructure required to deploy, run, and manage applications. Startups - For example, imagine you were a startup building the next social networking site or online game You have to worry about numerous issues that are unrelated to the functionality of the application.[Capacity]You have to think about the capacity requirements for the application.Will it be used by a few thousand users or hundreds of thousands or millions?How do users translate to bandwidth, storage, and server requirements?Will the usage be consistent during all times of the year? Will it be consistent over the lifetime of the application?Can you handle spikes in demand if there were sudden demands for the app? (Digg Effect)Ultimately, most organizations end up paying for more capacity then they need.[Deployment, operations, and versioning]Then you have to worry about deploying and operating your applicationHow do you deploy your application over multiple servers?How do you role out updates to the app without taking it offline?How do you manage patches? Enterprise - For established organizations, some of these decisions and problems may have already been addressed through a shared data center or an established staff and processes. However, in enterprise organizations we often find that apps are silos of their own servers. Established organizations also still have to spend a significant amount of capital and operations funding. IT resources are applied to maintaining applications rather than delivering new value and functionality. ISV - Finally, if you’re an ISV who builds applications for use by other businesses you have to worry about a number of additional problems. You have to think about your customer’s capacity, which gets factored into the cost of ownership. Often, your ability to sell your application is dependent on your customers ability to consume it.Your customers often have existing assets such as order fulfillment systems, ERP systems, multi-terabyte databases, etc. that are running on-premise. You must be able to easily integrate with these assets. So many things get in the way for building new appsInfrastructure - Operations, Patching, OS ManagementBuilding and maintaining costly infrastructureSo why is there so much hype around the cloud?When we talk with partners and customers, there are a few general reasons why they’re starting to find the cloud attractive. 1 - First, they view it as a way to reduce their capital and operations costs. A Cloud Platform provides a utility-like model to compute and storage resources – where organizations can only pay for what they use. This is often referred to as a “Pay as you go” model. 2 - Second, the cloud can potentially simplify the deployment and management of applicationsBy relieving organizations from worrying about infrastructure and capacity.3 - Cloud Services can improve time to market for new applications. Instead of spending weeks or months deploying servers and infrastructure to support new applications – organizations can quickly deploy applications to the cloud or use storage in the cloud where vendors provide pre-provisioned data centers.4 - Finally, Cloud Services can make it much easier to scale up or down as needed. Instead of building out capacity for peak usage or not having enough capacity to deal with usage spikes, with the cloud the platform vendor manages the capacity and you only use (and pay for) what you need. Think of this as “Pay as you grow”Notes:
- Slide objectives: Define the Microsoft Services Platform in a clear and repeatable way. Speaking Points: [Build-out the slide starting at the bottom]So what is Microsoft providing for the cloud?Applications provided as servicesMicrosoft has had a number applications that we’ve exposed to both user’s and organizations. For instance, today we have applications like Windows Live and Office Live that are operated as services.Within the last year we have also launched new online service versions of key products. This includes Exchange Online, SharePoint Online, and Dynamics CRM Online.These online applications provided as services enable IT organizations to rapidly use service-based versions of Microsoft products, without installing, configuring, and managing these products themselves.As part of providing SharePoint, for example, as a service, the SharePoint team had to think about a lot of issues such as:Scalability, redundancy, and availabilityProvisioning and billingAccess Control and federation of identities with existing on-premises systemsExtensibility – how do you let organizations customize and change an application running in a scalable, multi-tenant environment. We believe that these are common issues that we can address with a Cloud Platform.This is where the Azure Services Platform comes in. The Azure Services Platform is acomprehensive hosted platform for your applications & services. It enables a wide range of scenarios ranging from running your application code in Microsoft’s data centers to consuming programmable, web-based services from your applications.We are effectively building a comprehensive and coherent platform for the cloud, just as Windows & the .NET Framework provides a comprehensive and coherent platform for managed code.We are building a comprehensive services platform to help organizations take advantage of cloud computing and services.The Azure Services Platform consists of two layers of services:Windows AzureAt the base layer we have Windows Azure. Windows Azure provides the core data center and infrastructure as well as compute, basic storage, and management services. Effectively, Windows Azure allows you to run your code in Microsoft’s data center.Developer ServicesThe Azure Services Platform also provides a set of higher-level developer services including SQL Services, .NET Services, and Live Services.These higher-level services are programmable components, often exposed through standard SOAP or open REST-based endpoints, which can be consumed from within your applications. Your application can be running in Windows Azure and take advantage of these services or run on-premises or with a hosting provider.These services can also be mixed and matched to compose applications. In fact, you can selectively choose to just use certain services such as the .NET Services independent from the rest of the Azure Services Platform. Some of the services are designed more for business application scenarios and others are designed more for personal or consumer-centric scenarios. However, these services collectively will work together.These developer services include three primary categories:SQL Services – which are designed to provide the capabilities of SQL Server in the cloud.NET Services – which extend the key capabilities of the .NET Framework to provide flexible business connectivity, orchestration of services, and federated access control for your appsLive Services – which are designed to manage a user’s data and provide new user-centric capabilities to applications. SharePoint Services:Dynamics CRM and SharePoint are two of our most capable and most extensible platforms for business content, collaboration, and rapid solutions.The SharePoint Services and Dynamics CRM services you see on this diagram represent future services we will add to the Azure Services Platform. We will drill into Windows Azure, SQL Services, .NET Services, and Live Services later in this presentation. Notes:
- Slide objectives: Explain the three key themes and benefits of the Azure Services Platform.Speaking Points: There are three core themes that we are applying as we define the Azure Services Platform.1 - First, Azure is designed to be a Flexible Services Platform with Internet ScaleA flexible services and computing platform hosted from Microsoft’s data-centersFoundational Services: application computingBuilding Block Services: consumable web servicesDevelopers can choose what they want to use and how they use itISV, SI partner, web developer and enterprise usageUtilize services in existing applications, or consume in web applicationsA platform that is secure, reliable, includes developer tools, and support to make scale to 10 users or 10 million2 – Second, Azure is designed to provide Internet Standards Based and InteroperableStrata building block services use REST and SOAP standards so they can be called from other platforms and programming languagesDevelopers can create their own services and applications that conform to internet standardsSupport for Open ID, C#, Eclipse, IronPython and RubyRichest developer support on the Microsoft platform*Requires re-wording and additional support based on Strata Strategy Day feedback3 – Third, Azure can Extend Existing InvestmentsAugment what you have by reaching out and using the Building Block servicesSelectively expose what you have to business partners and the internetChoose what stays on-premises or off – applications still stay connectedStrata innovations are being incorporated into on-premises products for future feature parityNotes:
- Slide objectives: Ensure that the audience understands our experience and investments in running and operating services.Speaking Points: IntroMicrosoft hasn’t been running services quite as long as we’ve been making software – but we have been in the business for a while and at huge scale. Just a few numbers from our consumer businessLive Search: 2.16B queries per month, 41 languagesMSN: 550M unique users, 10B+ page views per monthLive ID: 1B+ Authentications/dayMessenger: 8.2B messages/dayMicrosoft has rapidly expanded its data center operations since embarking on the Software + Services strategy in 2005, and willcontinue to do so for the foreseeable future. Initially the company focused on leased facilities. Now we design and build our own data centers. These will soon be the largest and most advanced such facilities in the world—the Northlake facility near Chicago, for instance, will cover more than 500,000 square feet and deliver significant gains in energy efficiency and environmental performance. Data CentersThis is a listing of just the new Microsoft-owned data centers. Designing and building these facilities ourselves allows Microsoft greater control over power efficiency and related environmental impacts. The list below is partial; Microsoft does not comment on exactly how many data centers are operating worldwide. Quincy, WA: Complete, approx 500K sq ft, 27MW, uses entirely hydro-electric powerSan Antonio, TX: Opening Fall 08, approx 475K sq ft, 27MW, uses recycled water for coolingChicago, IL: Opening Spring/Summer 09, approx 550K sq ft, up to 60MW when full, 1st floor up to 220 double-stacked containers, 2nd floor standard raised-floor data center space, will use outside air for coolingDublin, Ireland: Opening Summer 09, approx 570K sq ft, up to 27MW, will use outside air for coolingDes Moines, Iowa: Recently announced purchase of land in the Des Moines area with the intent to build a data centerInnovation:With the Chicago data center, the entire first floor will house containerstrucks will haul up to 200 containers into the building and back them into their slotsFacilities personnel will hook up Internet connections and power and cooling equipment; then each of the containers will be up and runningContainers provide: Energy efficiency, Cost, Deployment speedNotes:
- Slide objectives: Ensure that the audience understands that Microsoft is continuing to invest in on-premises technologies and products. Speaking points: We have talked a lot in the past 20 minutes about the new Services Platform. However, what about Microsoft’s existing products?We believe that it’s important to have a choice. We consistently hear from organizations that they need to be able to run applications in both an on-premises environment and in the cloud. Today Microsoft provides a number of products such as Windows Server, SQL Server, and System Center that I am sure many of you are already familiar with. We will continue to invest in providing new features and functionality for these on-premises products.At the same time we are taking our investments and your investments in these products and extending them to the cloud with the Azure Services Platform. In fact, with Windows Azure, we are leveraging Windows Server 2008, IIS7, and Hyper-v to provide compute services.In doing so, we will add more features and functionality in the cloud to deal with challenges such as geo-scale, availability, redundancy, provisioning, and management. As we enhance the cloud offerings, these innovations will be pushed back into the codebase for our on-premises products.However, I do want to be clear that we are not focusing on or ensuring that the on-premises platform and the Azure Services Platform will be symmetrical. For developers, Visual Studio and the .NET Framework will be the common toolset, programming languages, and frameworks that will span both. Additionally, as we look forward at other technologies such as Oslo, we can see it playing a role in both the cloud and on-premises.Finally, we have heard from many partners such as many of you, that extending these products to the cloud and provide you new delivery models for your applications and leverage your existing investments. Notes: We are not providing the Azure Services Platform on-premises. Key messages:Consistent Programming ModelDevelopment skills transferInnovations push into bothWe are focusing on enabling you to compose solutions that use both the on-premises products you know and our customers have with the new Azure cloud services platform.
- Slide objectives: Define Windows Azure and explain the three types of services provided by Windows Azure.Speaking points: With Windows Azure, we are extending the Windows Server platform to the cloud Windows Azure is a scalable hosting environment for you to deploy your apps in our cloud.Windows Azure specifically consists of three core services:Compute – which provides virtualized compute environment based on Windows Server. Today we are running Windows Server 2008, Hyper-V, IIS7, and the .NET Framework 3.5 SP1. These are all technologies many of you are already familiar with today. Storage – which provides durable, scalable, & available storage with essential abstractions. There are three types of data supported in Windows Azure Storage – tables, blobs, and queues. Table support for structured data, but without the relational and query capabilities you find in a databaseBlobs can support very large sets of data such as images or videosQueues are used for communication between roles in Windows AzureManagement – Finally, the Management Services provide automated management of the infrastructure and your application. For instance, this service manages instance provisioning, application deployment, and changing service configuration.Today what you see surfaced in Windows Azure is a focus on applications. Currently this is limited to managed code for ASP.NET applications, WCF services, and worker processes.In the future we will provide support for unmanaged code and also virtual machines. Notes: