3. Agenda
What is Azure?
Under the hood of Azure
Architecting apps for Azure
4. “Packaged” Hosted “Software as a
Buy
Application “Packaged” Service”
Maximum
An application
that I buy “off the
An application
that I buy “off the
A hosted
application that
Build vs. Buy
Control
shelf” and run shelf” and then I buy from a
myself run at a hoster
vendor
Self Hosted Hosted Cloud Platform
“Home Built” “Home Built”
Maximum application
An
An application
that I develop and
Economy of Scale
An application
that I develop
that I develop
myself, but run
Build
run myself myself, but run at in the cloud
a hoster
On premises On premises vs. Cloud Cloud
5. Characteristics Of Cloud Computing
Scale-out not scale-up
Add and remove capacity on demand
Pay for what you use as you go
Automation is key to reducing costs
6. The Reality of Life
Business logic
…
Expand to new locale
Perform live upgrade for new feature
Apply OS patches Service “glue”
Diagnose service failures
and operations
Add storage capacity
Handle increase in traffic
Respond to hardware failures
Datacenter
7. What's Missing?
…. ……
Service 1 Service 2 Service 3 Service N
9. What Is Windows Azure?
It is an operating system for the cloud
It is designed for utility computing
It provides facilities to:
Write your apps (developer experience)
Host your apps (compute)
Manage your apps (service management)
Store your data (storage)
15. You tell the Fabric Controller what to
do, and it figures out how to do it.
16. For this to work, you need to tell us
about your application.
17. Defining Your Service
What are the components (roles)?
How do they interact?
At what scale?
Webrole
role
Webrole Worker role
Worker role
LB
Web Worker role
18. Putting It All Together
n m
LB
Web Role Worker Role
Cloud Storage (blob, table, queue)
19. Developer Experience is Key
Development
Offline cloud simulation
Visual Studio integration
Maintenance
Local debugging
APIs for logging
Management
APIs for configuration management
Web portal
21. Our Approach to Azure Services
Simple scenarios are simple – complex scenarios are possible
Services hosted in Microsoft’s data centers
Designed for high availability & scalability
Multiple protocol support including HTTP, REST, SOAP, AtomPub
Broad investment in open, community-based access to Azure services
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
24. Native Code & FastCGI
Run unmanaged code in your Azure hosted
applications
No longer limits development to .NET languages
Roles can
Select between partial trust or full trust
Call native library with P/Invoke
Spawn a sub-process
Setting in cloud projects .csdef file
A web role can now use IIS FastCGI module
26. Architecting apps for Azure
Remember that Azure manages Services not
servers
How do you deal with varying loads?
How do you deal with failures?
27.
28. Windows Azure Timeline
Today: Updated Technical Preview
Go get the CTP SDK bits and cloud access!
http://www.azure.com/windowsazure
Free usage with quotas
Thru CY 09: Regular updates
Late CY 09: Commercial availability
Business model
More features
29. Twitter: @tweval I would give #tncv-azure a 10.0
www.tweval.com/tncv-azure
30. Session References
Downloads
Windows Azure SDK
Windows Azure Tools for Microsoft Visual Studio
Azure Services Training Kit
Home Pages
Microsoft.com/azure
Cloud Computing Tools
Videos and Screencasts
Vertical axis is our classic build vs. buyHorizontal axis is new – on premise vs Cloud An application that I develop and run myselfAn application that I develop myself, but run at a hosterAn application that I develop myself, but run in the cloud (EC2 , AppEngine, Azure)An application that I buy “off the shelf” and run myselfAn application that I buy “off the shelf” and then run at a hosterA hosted application that I buy from a vendor ( Sales Force.com, CRM Live, SharePoint Online) If we have time left at the end, remind me to discuss an example of how an enterprise may look to leverage some of these options.
Services glue and operations is what we want from the cloud – we don’t care about itEconomy: Capital and Operation Expenditure (Cap Ex and Op Ex). Green computing: By making better use of resources computing per watt
You are never done
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: