aVs

Windows Azure

 Manuvir Das
Director
Microsoft
Corporation
Azure Services Platform
™
What Is The Cloud?

l A set of connected servers

l On which developers can:
l Install and run services
l Store and retrieve data
What Is Windows Azure?

l It is an operating system for the

cloud
l It is designed for utility computing
l It has four primary features:
l Service management
l Compute
l Storage
l Developer experience
Imagine Building A Desktop
Application In This Way:
l Select your hardware, wire it all
together
l Find some device drivers
l Write a file system
l Write a job scheduler
l Write an application installer
l…
l This would be a complete waste of
time!
But This Is What Every Cloud
Service Developer Has To Do
Today!
Busine ss lo gic
…
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
What's The Answer On The
Desktop?
An operating system:
l An application execution
environment
that abstracts away the
hardware
l A shared file system with access
control
l Resource allocation from a shared
pool
l Support for powerful
programming environments
l Inter-operability with other systems
What's Missing In The Cloud?
An operating system for the cloud:

…. ……
Service 1 Service 2 Service 3 Service N
What Should The Cloud OS
Provide?
l Thesame facilities that a desktop
OS provides, but on a set of
connected servers:
l Abstract execution environment
l Shared file system
l Resource allocation
l Programming environments
l And more: Utility computing
l 24/7 operation
l Pay for what you use
l Simpler, transparent administration
How Is The Cloud OS Manifested?

l Automated service management

l You define the rules and provide
your code
l The platform follows the rules:
deploys, monitors, and manages
your service
lA powerful service hosting
environment
l All of the hardware: servers; load
balancers; …
l Virtualized and direct execution
l Scalable, available cloud storage
l Blobs, tables, queues, …
 demo
The Cloud on
Your Desktop
Automated Service Management


Develop and Model Deploy and Run Maintain Service Health


l What’s in the model?

l Service topology and size
l Health constraints
l Configuration settings
Automated Service Management
Maintaining service health
l Abstraction is the key
l All resources are logical, and must
be declared in the service model
l Service code calls platform APIs to
map logical resources to physical
entities
l Service code then uses standard
APIs
l The OS can replace resources
transparently
l In the face of failures
l When performing upgrades
Automated Service Management
The bottom line

lA balance between power and ease

of use
l Write well behaved services,
reduce your TCO
l Designed for a full range of
scenarios, from
the hobbyist to the enterprise
developer
l But there is an escape hatch …
l In “Raw” mode, you can build your
own
VM and manage the service
yourself
l
Scalable, Available Cloud Storage

l Simple, essential storage

abstractions:
l Large items of user data: Blobs,
file streams, …
l Service state: Simple tables,
caches, …
l Service communication: Queues,
locks, …
l With an emphasis on:
l Massive scale, availability and
durability
l Geo-distribution and geo-
replication
l This is not a database service in
Rich, Familiar Developer
Experience
lA cloud environment on the
desktop
l Support for a variety
of programming languages
l ASP.NET, .NET languages, native
code, PHP
l An ecosystem of tools and support
l Integration with Visual Studio,
Eclipse
l Logging, alerts, tracing, …
l Samples, documentation, MSDN,
forums, …
l
Putting It All Together
Simple architectures for scalability

E xa m p le :

n m

Web Role Worker Role

LB

Cloud Storage (blob, table, queue)

Takeaways: Windows Azure Is

l Designed to encourage best

practices
l Stateless compute + durable
storage
l Co-location of computation and
data
l Queues for asynchronous
processing
l An open platform
l Connect outbound to any server
l Open protocols and APIs on all
components


l More information? Attend ES03

Evals & Recordings

e a s e fill T h is se
Pl ssio n
t y o u r
ou o n w ill b e
lu a ti a v a ila b
eva le a s
s
fo r th i a t: a re c o r
d in g
n
se ssio a t:

w w w . m icro so ftp d c . co m
 QA
&
Please use the microphones
provided