1. Windows Azure ‘Training’ Tokens
You should already have received an with the login information
Good for 1 month  Expires May 8th
No credit card; no commitments!
Meant for ‘trying out’ Windows Azure
After 1 month, transition strategy handled by regional Microsoft representative

2. Azure Access Requirements
Compute Hours
Data Storage
Blob
SQL Azure
‘Dallas’ data
As I talked to faculty last night
Don’t know
Want accounts for 4 students to probe further [Research]
Accounts for my class of 20 students [teaching]
Solution offering –
Highest denominator?
Mean?
Least common denominator?
So think of ’30-day’ account [ends may 8th] as a way to learn the Azure features and what aspects your work needs.
Let your Microsoft contact know what your needs are in
Research
Teaching

3. Windows Azure Platform
Architecting for the
Windows Azure Platform
Krishna Kumar
Twitter: KrishnaOnAzure

5. State of Cloud Computing
Perceptions
“The end of software”
On-demand infrastructure
Cheaper and better
Reality
Hybrid world; not “all-or-nothing”
Leverage existing IT skills and investments
Seamless user experiences
Evolutionary; not revolutionary
Drivers
Ease-of-use, convenience
Product effectiveness
Simplify IT, reduce costs
Types
Public
Private
Internal
External
Hybrid
Categories
SaaS
PaaS
IaaS

6. IT as a Service Private Infrastructure Platform (On-Premise)
You manage
Applications
Applications
Applications
You manage
Runtimes
Runtimes
Runtimes
Security & Integration
Security & Integration
Security & Integration
Managed by vendor
You manage
Databases
Databases
Databases
Servers
Servers
Servers
Managed by vendor
Virtualization
Virtualization
Virtualization
Server HW
Server HW
Server HW
Storage
Storage
Storage
Networking
Networking
Networking

7. Microsoft in the Cloud (6 years) (7 years) 4B emails/day (15 years)
5B conf
min/yr
(15 years)
450M+
active users
(11 years)
2B queries/mth
(11 years)
320M+ active
users
(12 years)
Largest non-
ICP/IP cloud service
x100M users
(13 years)
550M
users/mth
(15 years)
450M+
active users

8. Infrastructure Services
The Microsoft Cloud
Categories of Services
Application Services
Software Services
Platform Services
Infrastructure Services

9. Workload Patterns Optimal For Cloud
Usage
Compute
Time
Average
Inactivity
Period
“On and Off “
On & off workloads (e.g. batch job)
Over provisioned capacity is wasted
Time to market can be cumbersome
Average Usage
Compute
Time
“Growing Fast“
Successful services needs to grow/scale
Keeping up w/ growth is big IT challenge
Complex lead time for deployment
Compute
Time
“Unpredictable Bursting“
Average Usage
Unexpected/unplanned peak in demand
Sudden spike impacts performance
Can’t over provision for extreme cases
Compute
Time
Average Usage
“Predictable Bursting“
Services with micro seasonality trends
Peaks due to periodic increased demand
IT complexity and wasted capacity

10. But what about these new scenarios?

11. Consider these statistics:
EIGHTEEN months ago, Li & Fung 100GB of information flow through its network each day. Now the amount has increased tenfold
During 2009, American drone aircraft flying over Iraq and Afghanistan sent back around 24 years’ worth of video footage
When the Sloan Digital Sky Survey started work in 2000, its telescope in New Mexico collected more data in its first few weeks than had been amassed in the entire history of astronomy. Now, a decade later, its archive contains 140TB of information.
A successor, the Large Synoptic Survey Telescope, due to come on stream in Chile in 2016, will acquire that quantity of data every five days.
Wal-Mart, a retail giant, handles more than 1m customer transactions every hour, feeding databases estimated at more than 2.5PB — the equivalent of 167 times the books in America’s Library of Congress
Mankind created 150 exabytes (billion gigabytes) of data in This year, it will create 1,200 exabytes.

13. But, How does it work?

14. A 2-D Perspective Infrastructure App Dev Hardware Management
Servers
Storage
Networks
Management
Concurrency
Coordination
Fault Tolerance
Open API formats
Open Data Formats
Data Intensive Computing

15. Windows Azure An illustration
Application
Config
Storage
Compute
Fabric
.NET Services
Applications
SQL Azure
Windows Azure
Applications
Windows
Server
Windows
Vista/XP
Windows
Mobile
Others

16. a place to run your applications.
Windows Azure is
a place to run your applications.

17. a cloud computing platform, so it’s designed to scale.
Windows Azure is
a cloud computing platform,
so it’s designed to scale.

18. a utility computing platform, so you pay for what you use.
Windows Azure is
a utility computing platform,
so you pay for what you use.

19. Inside are many servers.

20. with VMs running Windows.

21. We call this the Fabric,

22. and it’s where your app runs.
Your Application

23. Windows Azure does scale out.

24. ----------------------------- = Scalable application
Stateless compute
+ Durable storage
= Scalable application

25. Storage is just another app.
Storage Service

26. Durable Storage Blobs Tables Queues Three replicas of everything
REST API
Blobs
Tables …
Queues

27. Storage Scalable & Available
Simple, essential storage abstractions:
Large items of data: Blobs, file streams, …
Service state: Simple tables, caches, …
Service communication: Queues, locks, …
With an emphasis on:
Massive scale, availability and durability
Geo-location and geo-replication
This is not a relational database in the cloud

28. Management tasks are automated by the
Fabric Controller.

29. You tell the Fabric Controller what to do, and it figures out how to do it.

30. For this to work, you need to tell us about your application.

31. What are the components (roles)? How do they interact? At what scale?
Defining Your Service
What are the components (roles)?
How do they interact?
At what scale?
Web role
Worker role
Web role
Worker role
Web role
Worker role LB

32. Putting It All Together
Web role
Worker role
Storage LB

33. Developer Experience is Key
Development
Offline cloud simulation
Visual Studio integration
Maintenance
Local debugging
APIs for logging
Management
APIs for configuration management
Web portal

34. Geo-location Windows Azure is in multiple “locales” You can:
Choose a locale for any of your applications
Create an “affinity group” to co-locate a set of applications from your cloud project
Available through the developer portal

35. Windows Azure Your Service Fabric Controller Web Portal (API) DNS LB

36. Service Deployment Your Service Service Service Service Model DNSLB
DNS
Service
Service
Service
Your
Service
Model
Web Portal
(API)
DNS
Fabric
Controller
config

37. Service Scaling Your Service Fabric Controller Model Web Portal (API)LB
DNS
Your
Service
Service
Service
Service
Service
Service
Service
Service
Service
Web Portal
(API)
Fabric
Controller
Model

38. Service Monitoring & RecoveryLB
DNS
Your
Service
Service
Service
Service
Service
Web Portal
(API) !
Fabric
Controller
Model

39. Putting It All Together Architectures for scalable, reliable services
4/2/2017 2:20 AM
Putting It All Together Architectures for scalable, reliable services
Example:
Cloud Storage
Web Role LB n
Worker Role m
© 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.

40. SQL Azure Formerly known as SQL Services
SQL Azure Database
Others (Future)
.NET Services
Applications
SQL Azure
Windows Azure
Applications
Windows
Server
Windows
Vista/XP
Windows
Mobile
Others

41. TechReady7 Breakout Chalktalk Template
4/2/2017
SQL Azure
Today:
SQL Azure Database
Formerly known as SQL Data Services (SDS)
And before that as SQL Server Data Services (SSDS)
“Huron” Data Hub
Built on the Microsoft Sync Framework
In the future:
Reporting
Analysis
Extract/Transform/Load (ETL) services
More
© 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.

42. SQL Azure Database An illustration
TDS
Database
SQL Azure Database
“Huron” Data Hub
Others (Future)

43. SQL Azure Database Using one or multiple databases
Application
Database
Database
Application

44. .NET Services Infrastructure in the cloud
Access Control ?
Service Bus
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 Service
Service 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 that you 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.
.NET Services
Applications
SQL Azure
Windows Azure
Applications
Windows
Server
Windows
Vista/XP
Windows
Mobile
Others

45. TechReady7 Breakout Chalktalk Template
4/2/2017
Service Bus
The problem: Exposing internal applications on the Internet isn’t easy
Network address translation (NAT) and firewalls get in the way
The solution:
Service Bus provides a cloud-based intermediary between clients and internal applications
Direct or queued
It also provides a service registry that clients can use to find the services they need
© 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.

46. Illustrating Service Bus
Registry
Endpoints
2) Discover endpoints
1) Register endpoints
3) Access application
Organization Y
Organization X
Application
Access Control
Service Bus

47. Application Models Web Hosting High Performance Computing
Massive scale infrastructure
Parallel & distributed processing
Burst & overflow capacity
Massive modeling & simulation
Temporary, ad-hoc sites
Advanced analytics
Application Hosting
Information Sharing
Hybrid applications
Reference data
Composite applications
Common data repositories
Automated agents / jobs
Knowledge discovery & mgmt
Media Hosting & Processing
Collaborative Processes
CGI rendering
Multi-enterprise integration
Content transcoding
B2B & e-commerce
Media streaming
Supply chain management
Distributed Storage
Health & life sciences
External backup and storage
Domain-specific services

48. Case Study Background Solution Benefits
Web-based ERP and accounting software to help mid-sized businesses automate customized business processes
Cloud-based SaaS deployment
Windows Azure
SQL Azure
Benefits
Business needs:
Application migration completed in 3 weeks with 2 developers
Launch a SaaS offering which includes on demand infrastructure and billing
Maintain a 24/7 production environment
Customers can implement solution without investing in on- premise infrastructure; can save ~$8,000 for startup costs
Minimize development efforts for both on-premise and SaaS offerings
Technical implementation
Lowered capital expenditures
Web – IIS 7, ASP.NET 3.5
Improved time-to-market and agility in meeting customer needs
Server – SQL Server 2005/2008, Windows Server 2003/2008
Tools – Visual Studio 2008, .NET Framework 3.5
More strategic use of IT resources

49. Case Study Background Solution Benefits
Online service providing productivity tools to help students conduct research, write better papers, and get help on-demand
Hybrid cloud application
Cloud-based extensions and services mash-ups with on- premise implementation
Technical implementation
Windows Azure application
Client – Windows Mobile 6
.NET Services service bus, access control, & workflows
Web – IIS 6, ASP.NET 3.5
Server – Windows Server 2003, SQL Server 2005
Benefits
Services – Bing Search, Windows Live Messenger Web Toolkit
$500,000 savings in dev. costs
40% faster time-to-market
Tools – Visual Studio 2008, .NET Framework 3.5, .NET Compact Framework 3.5
More effective development
Cost-effective scalability and enhanced availability

50. Case Study Browser FW—LB—Cache SQL Server Facebook Connect Integration
IE 6/7/8* and Firefox
Rich Web 2.0 Technologies:
Javascript
Java
Ajax
CSS
XHTML
Internet Clipping Toolbar
Full Featured Javascript Editor
JSON / AJAX/ HTTP
Eduify Workflows
Common Services
Notification
Logging
Security
Eduify
Business Objects
Facebook Connect Integration
FW—LB—Cache
Local / Network File Folder
ASP.NET / CLR
IIS
ASPX Pages
Third Party
Mashups
Bing Search Integration for Citation Check
SQL Server
Local Storage
Browser

51. Case Study Live Presence Cloud-Based Extensions
IM Integration
Search Citation / Plagiarism
Connected w/ Services
Mash-up with Microsoft Services
Cloud-Based Extensions
On-Premise Implementation
Certain ASPX | Workflows | Service Bus | Access Controls
ASP.NET
Workflows
Business
Objects
Common
Services
Service Bus
SQL Server
Local Storage

52. Case Study About Solution Benefits
kbb.com, established 1995; vehicle data aggregation and publication service provider
Cloud-based overflow capacity
Windows Azure Web Role
SQL Azure database
14M UU/month
Benefits
Multiple physical data centers
~$100,000 savings / year in hosting costs alone
Retire failover data center (27 Web servers & 9 SQL Servers)
<1% code changes needed for application compatibility
6 weeks down to 6 minutes to add server capacity

53. Case Study About Solution Benefits
Legacy call-center application for order processing and fulfillment
Cloud-based Web-enablement of on-premise assets
On-premise systems integration with ERP and master data management
Windows Azure Web Role
Web services integration via on- premise ESB endpoints
Benefits
“In a matter of weeks, we were able to see the fruits of our efforts very rapidly.“ – Kevin Flowers, Dir. Enabling Technologies
“The resilience and reliability of this platform is some of the benefits that we are seeing.” – Esat Sezer, SVP & CIO

54. Case Study About Solution Benefits
Complex Monte Carlo simulations to calculate financial risks
Massively scalable compute leveraging cloud capacity
Daily risk analysis load equivalent to processing 4 trillion US Stocks
Deployed on 2K Windows Azure instances; 10K+ in 2010
Existing on-premise HPC implementation
Windows Azure Worker Role
Windows Azure Blob and Queue
AppFabric Service Bus
Benefits
Elastic scaling to effectively meet customer demands
Turning elements of its peak load infrastructure from a fixed cost to a variable cost

55. Internet-Scale Application Architecture
Presentation
ASP.NET C#, PHP, Java
Distributed in-memory cache
Services
.NET C#, Java, native code
Distributed in-memory cache
Asynchronous processes
Distributed parallel processes
Transient file storage
Connectivity
Message queues
Service orchestrations
Identity federation
Claims-based access control
External services connectivity
SERVICE BUS
ACCESS CONTROL
WORK
FLOWS
Storage
Relational & transactional data
Federated databases
Unstructured, de-normalized data
Logical partitioning
Persistent file & blob storage
Encrypted storage

56. Application Patterns Cloud Web Application User Private Cloud
Web Browser
Mobile
Browser
Silverlight
Application
WPF
Application
Private Cloud
Public Cloud Services
Enterprise Application
ASP.NET
(Web Role)
ASP.NET
(Web Role)
Web Svc
ASP.NET
(Web Role)
Jobs
(Worker Role)
Application
Service
Enterprise Web Svc
Data
Service
Table Storage
Service
Blob Storage
Service
Queue
Service
Enterprise Data
Storage
Service
Enterprise Identity
Identity
Service
User
Data
Application
Data
Reference Data
Service Bus
Access Control Service
Workflow
Service

57. Application Patterns Composite Services Application User Private Cloud
Web Browser
Mobile
Browser
Silverlight
Application
WPF
Application
Private Cloud
Public Services
Enterprise Application
ASP.NET
(Web Role)
ASP.NET
(Web Role)
Web Svc
ASP.NET
(Web Role)
Jobs
(Worker Role)
Application
Service
Enterprise Web Svc
Data
Service
Table Storage
Service
Blob Storage
Service
Queue
Service
Enterprise Data
Storage
Service
Enterprise Identity
Identity
Service
User
Data
Application Data
Reference Data
Service Bus
Access Control Service
Workflow
Service

58. Application Patterns Cloud Agent Application User Private Cloud
Web Browser
Mobile
Browser
Silverlight
Application
WPF
Application
Private Cloud
Public Services
Enterprise Application
ASP.NET
(Web Role)
ASP.NET
(Web Role)
Web Svc
ASP.NET
(Web Role)
Jobs
(Worker Role)
Application
Service
Enterprise Web Svc
Data
Service
Table Storage
Service
Blob Storage
Service
Queue
Service
Enterprise Data
Storage
Service
Enterprise Identity
Identity
Service
User
Data
Application Data
Reference Data
Service Bus
Access Control Service
Workflow
Service

59. Application Patterns B2B Integration Application User Private Cloud
Web Browser
Mobile
Browser
Silverlight
Application
WPF
Application
Private Cloud
Public Services
Enterprise Application
ASP.NET
(Web Role)
ASP.NET
(Web Role)
Web Svc
ASP.NET
(Web Role)
Jobs
(Worker Role)
Application
Service
Enterprise Web Svc
Data
Service
Table Storage
Service
Blob Storage
Service
Queue
Service
Enterprise Data
Storage
Service
Enterprise Identity
Identity
Service
User
Data
Application Data
Reference Data
Service Bus
Access Control Service
Workflow
Service

60. Application Patterns Grid / Parallel Computing Application User
Web Browser
Mobile
Browser
Silverlight
Application
WPF
Application
Private Cloud
Public Services
Enterprise Application
ASP.NET
(Web Role)
ASP.NET
(Web Role)
Web Svc
ASP.NET
(Web Role)
Jobs
(Worker Role)
Application
Service
Enterprise Web Svc
Data
Service
Table Storage
Service
Blob Storage
Service
Queue
Service
Enterprise Data
Storage
Service
Enterprise Identity
Identity
Service
User
Data
Application Data
Reference Data
Service Bus
Access Control Service
Workflow
Service

61. Application Patterns Hybrid Enterprise Application User Private Cloud
Web Browser
Mobile
Browser
Silverlight
Application
WPF
Application
Private Cloud
Public Services
Enterprise Application
ASP.NET
(Web Role)
ASP.NET
(Web Role)
Web Svc
ASP.NET
(Web Role)
Jobs
(Worker Role)
Application
Service
Enterprise Web Svc
Data
Service
Table Storage
Service
Blob Storage
Service
Queue
Service
Enterprise Data
Storage
Service
Enterprise Identity
Identity
Service
User
Data
Application Data
Reference Data
Service Bus
Access Control Service
Workflow
Service

62. Internet-Scale Application
2007 stats:
+20 petabytes of data processed / day by +100K MapReduce jobs
1 petabyte sort took ~6 hours on ~4K servers replicated onto ~48K disks
+200 GFS clusters, each at 1-5K nodes, handling +5 petabytes of storage
~40 GB/sec aggregate read/write throughput across the cluster
+500 servers for each search query < 500ms
Scaling the process:
MapReduce: parallel processing framework
BigTable: structured hash database
Google File System: massively scalable distributed storage
Source: Jeffrey Dean and Sanjay Ghemawat, Google

63. Internet-Scale Application
2009 stats:
+200B pageviews/month
+20B photos, +2B/month growth
>3.9T feed actions/day
600,000 photos served / sec
+300M active users
25TB log data / day processed thru Scribe
>1B chat mesgs/day
120M queries /sec on memcache
100M search queries/day
>6B minutes spent/day (ranked #2 on Internet)
Source: John Rothschild, VP of Technology, Facebook
Scaling the “relational” data:
Keeps data normalized, randomly distributed, accessed at high volumes
Uses “shared nothing” architecture

64. Internet-Scale Application Architecture
Design
Data & Content
Horizontal scaling
De-normalization
Service-oriented composition
Logical partitioning
Eventual consistency
Distributed in-memory cache
Fault tolerant (expect failures)
Diverse data storage options (persistent & transient, relational & unstructured, text & binary, read & write, etc.)
Security
Claims-based authentication & access control
Processes
Federated identity
Loosely coupled components
Data encryption & key mgmt.
Parallel & distributed processing
Management
Asynchronous distributed communication
Policy-driven automation
Aware of application lifecycles
Idempotent (handle duplicity)
Handle dynamic data schema and configuration changes
Isolation (separation of concerns)

65. Infrastructure Services
The Microsoft Cloud
Categories of Services
Application Services
Software Services
Platform Services
Infrastructure Services

66. Windows Azure for Application Developers
SDK
Portal
Hosted
Service
Storage
Develop
Deploy
Run

67. Roles
Role
Code
Configuration

68. Load Balanced Instances
Role
Instance 1
Instance 2

69. Web vs Worker Role Web Role Worker Role IIS Host System Host Your Code

70. Storage
Storage
Queue
Blob
Account
Tables

71. Blobs
Containers
Blobs
Photo1.png
Photo2.png
Pictures
Photo3.png

72. Queues
Queues
Messages
“Body1”
“Body2”
ThumbnailJobs
“Body3”

73. Development Fabric and Storage
Local Machine
Windows Azure Simulation Environment
Development Fabric
Development Storage

74. Portal

75. Hello Cloud
Web Role
Worker Role
Queue
Blob

76. Hello Cloud – Web Role
Web Role

77. What We’re Going To Code

78. What We’re Going To Code
Step 1 - Create a Cloud Service project with a Web Role
Step 2 - Write our code and test it locally
Step 3 – Deploy to the Cloud

79. Web Role
Demo

80. Portal – Allocated

81. Portal - Run

82. Portal - Initializing

83. Portal - Busy

84. Portal - Ready

85. Hello Cloud – Blobs and Queues
Web Role
Enqueue Message
Queue
Upload Blob
Blob

86. What We’re Going To Code
Step 1 – Configure a Storage Account
Step 2 – Upload a Blob
Step 3 – Enqueue a Message

87. Blob + Queue
demo

88. Hello Cloud – Worker Role
Dequeue Message
Queue
Update Blob
Blob

89. What We’re Going To Code
Step 1 – Add a Worker Role
Step 2 – Dequeue Next Message
Step 3 – Update the Blob referenced in the message
Step 4 – Delete Message from Queue

90. Worker Role
demo

91. Hello Cloud
Web Role
Worker Role
Queue
Blob

92. New Project

93. Add a Role

94. Write Some Code

95. Run and Debug Locally (Hit F5)

96. Deploy to the Cloud

97. Create Your Accounts

98. Deploy Your Service

99. And You’re Running

100. Same Development Tools and Experience
Summary
Same Development Tools and Experience
Local and Cloud Based Environments
Rapid Cloud Development, Deployment and Maintenance

101. Windows Azure ‘Compute’
Under the hood:
Windows Azure ‘Compute’

102. Windows Azure Push-button Deployment
Step 1: Allocate nodes
Across fault domains
Across update domains
Step 2: Place OS and role images on nodes
Step 3: Configure settings
Step 4: Start Roles
Step 5: Configure load-balancers
Step 6: Maintain desired number of roles
Failed roles automatically restarted
Node failure results in new nodes automatically allocated
Allocation across fault and update domains
Load-balancers

103. High-Level Architecture
Host Partition
Guest Partition
Guest Partition
Applications
Applications
Virtualization Stack
(VSP)
Drivers
Host OS
Server Core
Virtualization Stack
(VSC)
Guest OS
Server Enterprise
Virtualization Stack
(VSC)
Guest OS
Server Enterprise
VMBUS
VMBUS
VMBUS
Hypervisor
Hardware
NIC
Disk1
Disk2
CPU

104. Image-Based Deployment
Maintenance OS
Host Partition
Guest Partition
Guest Partition
Guest Partition
Application VHD
Application VHD
Application VHD
App1 Package
App3 Package
App2 Package
Host partition differencing VHD
Guest partition differencing VHD
Guest partition differencing VHD
Guest partition differencing VHD
HV-enabled Server Core base VHD
Server Enterprise base VHD
Server Enterprise base VHD
Server Core base VHD

105. Service Isolation And Security
Your services are isolated from other services
Can access resources declared in model only
Local node resources – temp storage
Network end-points
Isolation using multiple mechanisms
Automatic application of Windows security patches
Rolling OS image upgrades
Managed code
Restriction of privileges
Firewall
Virtual Machine
IP filtering

106. Fault Domains Purpose: Avoid single points of failures
Unit of a failure
Examples: Compute node, a rack of machines
System considers fault domains when allocating service roles
Example: Don’t put all roles in same rack
Service owner assigns number required by each role
Example: 10 front-ends, across 2 fault domains
Fault domains
Allocation is across fault domains

107. Update Domains Purpose: ensure service stays up while updating
Unit of software/configuration update
Example: set of nodes to update
Used when rolling forward or backward
Developer assigns number required by each role
Example: 10 front-ends, across 5 update domains
Update domains
Allocation is across update domains

108. Platform of Choice

109.
Sign up at the Windows Azure Platform developers’ portal
Windows Azure access
Developer tools
White papers
Sample applications
Plan pilot applications, proofs of concept, and architectural design sessions with Windows Azure partners
Build and deploy software quickly and easily by capitalizing on the same personnel, development tools investments, and knowledge that already power your IT organization. Use the services platform’s infrastructure to power prototyping environments for experimentation, and then launch to full-scale production as soon as your business needs it. Imagine connecting existing applications with an online database that can be shared with partners, or a service bus that enables secure B2B connectivity across firewalls.
Pay as you grow and reduce costs. Pay for the services you use and reduce the capital costs associated with purchasing hardware and infrastructure. Reduce operational costs by running applications on the services platform and decrease the need for maintaining on-premises infrastructure. Increase business efficiency and agility by dynamically adding and subtracting capacity in real time. Envision building an e-commerce Web site that you can scale at the click of a mouse to meet seasonal demands or spikes in traffic based on sales and promotions.
Develop a new portfolio of expertise. In these early stages of software development for the cloud, businesses will be seeking the best advice on what this means for their current and future technology investments. Stay ahead of the curve and help your customers understand what cloud computing and development means to their business today and how they can pivot and extend their investments to maximize its value tomorrow.
Don’t slow down. Start projects without the hurdles of lengthy training or waiting for new infrastructure to be delivered and installed. With a broad set of services already running on Microsoft global data centers, the services platform is ready to start prototyping and testing solutions.

110. Thank you krishna.kumar@microsoft.com http://azurepilot.com
© 2009 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.