This document discusses different service models in cloud computing including Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). It outlines the key characteristics of each model in terms of what is managed by the cloud provider versus the customer. For example, in IaaS the customer manages the applications, data, and some middleware while the provider manages the infrastructure including servers, storage, networking, and virtualization. PaaS provides additional managed services like runtime, middleware, and operating system. In SaaS, the provider manages everything except custom applications and some configuration settings.

4. Non-Service Infrastructure Platform Software
Approach (as a Service) (as a Service) (as a Service)
You manage
Applications Applications Applications Applications
You manage
Data Data Data Data
Runtime Runtime Runtime Runtime
Managed by provider
Middleware Middleware Middleware Middleware
You manage
Managed by provider
O/S O/S Managed by provider O/S O/S
Virtualization Virtualization Virtualization Virtualization
Servers Servers Servers Servers
Storage Storage Storage Storage
Networking Networking Networking Networking

5. Vision Go Inside Containers Energy Efficient
North American Data Centers European Data Centers Asian Data Centers
Dublin
Chicago
Amsterdam
San Antonio
Hong Kong
Singapore

7. Platform

10. Business
Reporting Data Sync
Analytics

12. WEB & CLOUDS
Compute Storage Management Relational data Management Connectivity Access control
ON-PREMISES

13. Development
Azure SDK AppFabric SDK
Environment
• OS: Vista+ • Provides local devfabric • Provides libraries and
• Must enable local IIS and dev storage tools to use ACS and
features • Complete local Service Bus
• Visual Studio 2008+ simulation of the cloud • Includes ACM.exe and
• Must run as local fabric AF Configuration
Admin • 90% of the local Management Browser
devfabric is the same as source.
• .NET 3.5 sp1
the cloud fabric
• Local SQL instance
• Includes handy project
templates
• Deployment and
management tools
• Includes client storage
library

14. The Fabric Controller
• Automates load balancing and computes
resource scaling.
• It communicates with every server within
the Fabric.
• Monitors application and optimizing
hardware utilization.
Computation = CPU Storage Services
• Provides application • Store large amount of
scalability. data
• Web and Worker roles. • Format from Image to
• Scale Up and Down the text
processing power. • Paying for what they use
or store.

15. Fabric Controller
• Interacts with a “Fabric
Agent” on each machine
• Monitors every VM,
application and instance
The Fabric Controller • Performs load balancing,
automates service check pointing and recovery
management

16. Compute in Windows Azure
GOAL:
SCALABILITY Two instance types: Web Role & Worker Role
Windows Azure applications are built with
Scale out by replicating instances as web role instances, worker role instances,
needed. or a combination of both.
Allow applications to scale
user and compute processing
independently.
Each instance runs on
its own VM (virtual
machine), replicated as
needed.

17. GOAL:
SCALABLE, DURABLE
STORAGE Tables: simply Queues: serially accessed
structured data,
Blobs: large, messages
accessed using
unstructured or requests, allowing
Windows Azure storage is an data (audio,
ADO.NET Data web-roles and worker-
application managed by the Services
video, etc) roles to interact
Fabric Controller
Windows Azure applications can use
native storage or SQL Azure
Each item in storage is stored in triplicate.

19. Your
Service
D
N
S
L
B
Web Portal
(API)
L
Fabric B
Controller

20. Your
Service Model
Service
D
N
S
L
B
Web Portal
(API)
DNS
config L
Fabric B
Controller

21. Your
Service Service
D
Service
N
S
Service
Service Service
L Service
B
Service
Service
Web Portal
(API)
L
Fabric B
Controller
Model

22. Your
Service
D
Service
N
S
Service
L
B Service Service
Web Portal
(API)
L
Fabric B
Controller
Model

23. WEB & CLOUDS
Compute Storage Management Relational data Management Connectivity Access control
ON-PREMISES

25. Account
Server
Database

27. !
Replica 1
Replica 2
DB
Replica 3
Replica 4

28. Deployment
DB SQL Azure
Script TDS
Gateway

29. Accessing databases
Change Connection String
Your SQL Azure
TDS
App Gateway

30. Applications use standard SQL
Application client libraries: ODBC, ADO.Net,
…
TDS (tcp:1433)
Load balancer forwards „sticky‟
Load Balancer sessions to TDS protocol tier
TDS (tcp: 1433)
Gateway Gateway Gateway Gateway Gateway Gateway
TDS (tcp: 1433)
Data Node Data Node Data Node Data Node Data Node Data Node
Scalability and Availability: Fabric, Failover, Replication and Load balancing

31. DBA role places more focus on logical management

32. WEB & CLOUDS
Compute Storage Management Relational data Management Connectivity Access control
ON-PREMISES

33. Q&A
Ask your questions.
Azure Boot Camp

34. Azure Boot Camp