Azure Overview Business Model Overview

August 2009 | Page 1MICROSOFTMICROSOFT

Raj RamabadranPlatform Strategy AdvisorDeveloper & Platform [email protected]: http://rajramabadran.wordpress.com

mailto:[email protected]

http://rajramabadran.wordpress.com/

August 2009 | Page 2MICROSOFT

Agenda

• Introduction • What is Windows Azure, Business Model A• Azure Application Scenarios


Fixed and ongoing infrastructure costs distract from the mission of reducing business process friction

Leveraging past investments to provide future value

Many data centers at limit—real estate, capacity, cooling and power

Matching capacity to demand

1 Maintaining security while increasing access and transparency—within and outside the organization

2

3

4

5

6

7

1

Security, access, and transparency across the value chain: suppliers, partners, etc.

Lack of a common platform

Cloud-Addressable ChallengesChallenges Facing Today’s Enterprise


Challenges Building Apps

• # of users? After 1 month? 6 months? 1 yr? • Capacity? Servers? Bandwidth? Storage?• How do you scale up or down over time?• How can you handle peak loads?• How do you provide high availability?• What are the upfront capital costs?• How quickly can you go live?• How do you reduce your operations costs


TIME

IT C

APA

CIT

Y

Actual Load

Allocated IT-

capacities

“Waste“ of capacities

“Under-supply“ of capacities

Fixed cost of IT-capacities

Load Forecast

Barrier forinnovations

And in a non-cloud view, there are inefficiencies


However, in a cloud view

Actual Load

Allocated IT capacities

Reduction of initial

investments

Reduction of “over-

supply“

No “under-supply“

Possible reduction of IT-capacities

in case of reduced load

Time

IT C

APA

CIT

YLoad

Forecast


Off PremisesOn Premises

ScaleOut

Automated Service

Management

High Availability

Multi-Tenancy

Location

Considerations

Infrastructure

Business model

Ownership

Management

HomogeneousHeterogeneous

CapEx OpEx

Own Lease/Rent

Self Third Party

5 Difference between Legacy and Cloud Computing

Fundamentals


ON-PREMISES WEB & CLOUDS Third party cloudWeb applications

LOB ApplicationsComposite applications

Compute Storage Management

ManagementRelational data Connectivity Access control

Developer ExperienceUse existing skills and tools

Introducing the Windows Azure Platform


Defining the Web and Worker Roles

WEB ROLE WORKER ROLE

Interacts with end-useror web services

Handles incomingHTTP/HTTPS requests

Develop with Microsoft andnon-Microsoft tools:

ASP.NET, WCF, other .NET toolsJava, PHP, etc.

Does not acceptincoming requests

Initiates their own requestsfor data or tasks from

the queue

Similar to a "batch job"or Windows service


Building Solutions with the Windows Azure Platform

SQL Azure: Scalable, relational, Cloud-enabled database services

.NET Services: Framework for access control and communication between Cloud-aware applications


Defining Windows Azure Architecture

Fabric

Compute Storage

Fabric controller

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


Windows Azure

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.

The Fabric Controller automates load balancing and computes resource scaling

Security and Control Features include storage encryption, access authentication, and over-the-wire encryption using HTTPS. Industry certification is part of the Windows Azure roadmap.

State-of-the-art data centers located around the world host your applications and data, internet-accessible from everywhere you choose to allow.


Compute in Windows Azure

GOAL:SCALABILITYScale out by replicating worker instances as needed.

Allow applications to scale user and compute processing independently.

Two instance types: Web Role & Worker RoleWindows Azure applications are built with web role instances, worker role instances, or a combination of both.

Each instance runs on its own VM (virtual machine), replicated as needed


Net New Application /

Service

Optimizing Existing

Application / Service

Scalable Web-Apps

(Web)

Scalable Multi-Channel Apps(Middle-tier,

OLTP)

Storage(Archiving)

• Brand Website• Gaming Platform• Blog Platform • Real-time media streaming • Stored media streaming distribution • Social Networking

• Digitization of Media• E-Discovery (Analytics) • Media trans-coding & post-processing• Combinatorial drug analysis/research

• Back-ups• Archiving – Cold

Compute

Windows Azure platform Example Scenarios

• Channel integration and customer management for retail

• Electronic payment platform for Financial Services

• Payroll• Supply and distribution for Transportation• Collaboration and knowledge management• Productivity suite platform• Customer inquiries (Customer Service)• Accounts payable / receivable• Collaborative R&D environment for Pharma• E-Market Platform• E-Shopping


Comprehensive SLAsDependable performanceYears of Microsoft Experience

Faster time to marketSpeedier developmentSimpler deployment

Rapid monetization Scalability without complexity Fewer operational hurdles

On-demand computingElimination of idle IT capacityLower TCO

Windows Azure Benefits


Pay for What You Use–Use Only What You Need

Customer pricing model based on usage meters


SUBSCRIPTION

Azure Services Purchasing Models

*PDC scheduled for November 2009

CONSUMPTION VOLUME LICENSING“Pay as you go and

grow”Available at PDC*

launch Low barrier to entry and flexibilityOptimized for cloud elasticity

Discounts for commitmentPlans for payment predictability

“Coordinated purchasing”

Planned for post PDC* Unified purchasing through EA

Introduction to volume discounts

“Value for a commitment“

Select offers at PDC*


Windows Azure Pricing Meters

Virtual Machine instancesLoad balancers, routers, etc.Relational DB instancesService Management

- Fabric controller operations (deploy/upgrade/delete/scale)

- Load balancer programming

COMPUTE STORAGE BANDWIDTH

PRICE$0.12 / hourRDBMS Instance higherNo separate charge for service management

Blob StorageTable StorageMultiple replicasGeo-distributionDrives

PRICE$0.15 / GBStorage Transactions:

$0.01 / 10k

Ingress/Egress (to/from internet only)

PRICEBandwidth: $0.10 in / $0.15 out / GB


WEB EDITION

$9.99 / Month(1 GB)

Per database / month

BUSINESS EDITION

$99.99/ Month(10 GB)

Per database / month

BANDWIDTHPer GB transferred

$0.15 GB Egress

$0.10 GB Ingress

SQL Azure Pricing Models


$0.15 / 100K

BANDWIDTH

Per GB transferred

MESSAGESPer transactions

$0.10 GB Ingress

$0.15 GB Egress

.Net Services Pricing Meters


Users experience consistency from PCs and web browsers to mobile devices to servers

Enable developers to use familiar toolsets to reduce

time to market for new applications

Easily integrate solutions with a variety of

web-scalable services

Automatically manage applications

Software + Services


© 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.

Thank you

Snap my Vcard get free app for your phone at:http://www.microsoft.com/tag/

Technology

Azure Overview Business Model Overview