MODULE-II

Service Delivery and

Deployment Models
 CLOUD REFERENCE MODEL
Cloud computing supports any IT service that can be consumed as a utility and it is
delivered through the network, most likely the Internet. Such characterization
includes quite different aspects: infrastructure, development platforms, application
and services
Pure SaaS

Cloud Applications
SaaS

User
Applications Social Computing, Enterprise ISV, Scientific Computing, CDNs

Cloud Programming Environment and Tools

PaaS
Pure PaaS

Autonomic Cloud Economy

User-level Web 2.0, Mashups, Concurrent and Distributed Programming,

Adaptive Management
Middleware
Workflows , Libraries, Scripting

Cloud Hosting Platforms

IaaS

QoS Negotiation, Admission Control, Pricing, SLA Management,

IaaS (M)

Monitoring, Execution Management, Metering, Accounting

Core
Middleware
Virtual Machine (VM), VM Management and Deployment

Cloud Resources
System
Infrastructure
 Architecture
• It is possible to organize all the concrete
realizations of Cloud computing into a layered
view covering the entire stack from the

Pure SaaS
Cloud Applications

SaaS
hardware appliances to software systems. User
Applications Social Computing, Enterprise ISV, Scientific Computing, CDNs

• Cloud resources are harnessed to offer Cloud Programming Environment and Tools

PaaS
Pure PaaS
“computing/horse power” required for

Autonomic Cloud Economy

User-level Web 2.0, Mashups, Concurrent and Distributed Programming,

Adaptive Management
Middleware
Workflows , Libraries, Scripting
providing services.
• Often, this layer is implemented by using a Cloud Hosting Platforms

IaaS
QoS Negotiation, Admission Control, Pricing, SLA Management,

IaaS (M)
datacenter in which hundreds and thousands Core
Monitoring, Execution Management, Metering, Accounting

of nodes are stacked together. Cloud Middleware

Virtual Machine (VM), VM Management and Deployment

infrastructure can be in heterogeneous nature Cloud Resources

as variety of resources such as clusters and System
Infrastructure

even networked PCs can be used to build it.

• Moreover, database systems and other storage
services can also be part of the infrastructure.
• The physical infrastructure is managed by the
core middleware whose objectives are to
provide an appropriate runtime environment
for applications and to utilize resources at best.
3
 Architecture
• At the bottom of the stack, virtualization
technologies are used to guarantee runtime
environment customization, application isolation,
sandboxing, and quality of service.
•

Pure SaaS
Cloud Applications
Hardware virtualization is the most commonly used

SaaS
User
Applications Social Computing, Enterprise ISV, Scientific Computing, CDNs
at this level. Hypervisors manage the pool of
resources and expose the distributed infrastructure Cloud Programming Environment and Tools

PaaS
Pure PaaS

Autonomic Cloud Economy

User-level Web 2.0, Mashups, Concurrent and Distributed Programming,
as a collection of virtual machines.

Adaptive Management
Middleware
Workflows , Libraries, Scripting
• By using virtual machine technology it is possible to Cloud Hosting Platforms

IaaS
finely partition the hardware resources such as CPU, QoS Negotiation, Admission Control, Pricing, SLA Management,

IaaS (M)
Monitoring, Execution Management, Metering, Accounting
memory, and also virtualize specific devices, thus Core

meeting the requirement of users and applications. Middleware

Virtual Machine (VM), VM Management and Deployment
• The combination of Cloud hosting platforms and Cloud Resources
resources is generally classified as a Infrastructure- System

as-a-Service (IaaS) solution. Infrastructure

• Infrastructure-as-a-Service solutions are suitable for

designing the system infrastructure but provide
limited services to build applications.
• Such service is provided by Cloud programming
environments and tools, which form a new layer for
offering to users a development platform for
application
4
 Service Models
XaaS

As time goes by, more and more “as a service” models are being introduced. Since there are so many of
them, we can be said to be heading into the “X” as a service or “XaaS” era.

X = Anything OR Everything.

• Software as a service
• Platform as a service
• Infrastructure as a service
• Storage as a service
• Mobility as a service
• Database as a service
• Communications as a service
• Network as a service
• Desktop as a Service (DaaS)
• Process as a Service
CLOUD SERVICE MODELS
Saas

On demand Service

Independent Platform

No need to install on PC

Resources managed by Vendor

Who uses it?

End Customers
 Saas
Pros Cons
• Universally accessible from
any from any platform • Portability

• Excellent for collaborative • Browser issues

working
• Compliance Restrictions
• Vendor provides modest
software tools
• Internet dictates overall
• Allows for Multi tenancy. performance.
SaaS Examples
Paas
Programming Language +OS+Server+Database

Provides Encapsulation

Build , Compile & Run Programs

Users manage data and application resources

Who uses it?

Developers
 Paas
Pros Cons
• Scalable and Cost effective
• Provider Languages only
• Faster Market for
developers • Developers Limited

• Easy deployment of web • Migration issues

applications

• Vendor Lock-in
• Private and public
deployment
• PaaS Examples
Iaas/Haas
Provides architecture and Infrastructure

Data storage + Virtualization + Servers + Networking

Vendors manage above resources

Users handle data & middle ware

Who uses it?

System administrators
Iaas
Pros Cons
• Cloud provides the
infrastructure • Security Issues

• Enhanced Scalability • Service delays

• Dynamic workloads are • Network delays

supported

• Flexible
Iaas Examples
Comparisions
Summary of Classification of Service Models