2. 2
Agenda
Introduction
Evolution of Computing
Compare with Traditional Server
Compare with Virtualization Server
Cloud Computing Advantages / Benefits
Cloud Computing Types
Service Models
Summary
3. 3
Evolution of Computing
Client / Server - Distributed
Web Services – Internet Technology
Grid Computing – HPC
Utility Computing – Metered
Service
Cloud Computing
Next Generation
Mainframe –
Centralized
4. 4
Introduction
Cloud is Internet-based computing, whereby
shared computing resources (e.g., networks,
servers, storage, application and other
services) that can be rapidly provisioned and
released with minimal management effect.
5. 5
The Traditional Server Concept
Pros
Easy to conceptualize
Fairly easy to deploy
Easy to backup
Virtually any
application/service can be
run from this type of
setup
Cons
Expensive to acquire and
maintain hardware
Not very scalable
Difficult to replicate
Redundancy is difficult to
implement
Vulnerable to hardware
outages
In many cases, processor
is under-utilized
6. 6
The Traditional Virtualization Concept
Pros
Resource pooling
Highly redundant
Highly available
Rapidly deploy new
servers
Easy to deploy
Reconfigurable while
services are running
Optimizes physical
resources by doing more
with less
Cons
Slightly harder to
conceptualize
Slightly more costly (must
buy hardware, OS, Apps,
and so on...)
Difficult auto scaling
7. 7
Technologies for Agility
Virtualization
The ability to run multiple Operating System on
single physical system and share the underlying
hardware resources.
Utility Computing
Offering computing resources as a metered service
9. 9
Cloud Computing Advantages
On Demand Services
Speed of Delivery
Cost / Benefit ratio
Software as a Subscription
Reduced Software Maintenance
Increased Scalability
Elastic Nature
User have full control over their instance
10. 10
Benefits
Lower total cost operations (Pay-As-You-Go)
Save Infrastructure setup & Maintenance
Rapid, Request-driven provisioning
Easy monitoring, managing & reports
Storage and Retrieval of data
Uninterrupted and Persistent Data Storage
High Availability
Automated and even distribution of traffic
Flexible scaling of Resources
11. 11
Cloud Computing Characterized
Consumer Perspective
Single point of access - Self services with rich user experienced
Virtualization - Increased system utilizations
Automation - Automated service request and fulfillment
Agility - Rapid Services provisioning
Flexibility - Massive scaling of IT services as
needed
Usage Account - Utility based usage metrics
Service Management - Modular services managed access
Infra/Platforms/application/business
stacks
Security - Shared services delivered across trusted
domains
Cost Efficiency - Reduced CapEx with minimal to no asset
ownership
13. 13
Public Cloud
Infrastructure provisioned on-demand using
publicly available resources.
Computing resources are provided to
customers through self-serve interface.
Scalable computing resource on a temporary
or periodic basis.
Ability to acquire access to highly-quality
pools of resources immediately and with
minimal capital investment.
14. 14
Public Cloud Benefits
Reduce Infrastructre cost and maintain cost
Rapidly increase on-demand services,
storage capacity and other need
Public cloud available anywhere, anytime
Scalable to meet individal or company needs
High redundancy and available
15. 15
Private Cloud
Private cloud avail within the corporate
firewall using their own hardware.
Flexible to organization needs.
The Cloud architecture is dedicated to the
organization and is not shared with other
organization.
16. 16
Private Cloud Benefits
Data will be safe and secure
Scalable Bandwidth Access
Suitable and highly support SLA
Reliability
17. 17
Hybrid Cloud
Hybrid Cloud = Private Cloud + Public Cloud
Private cloud can extends their boundaries to
access additional computing resources in the
public cloud using secure communication
(VPN).
18. 18
Hybrid Cloud Benefits
Flexible computing resources
Continued reduction of cost expenses
Improved resource utilization and more
efficient system
19. 19
Community Cloud
A Cloud infrastructure that is shared by
several organizations
Often delivered securely via private network.
Ability to bill the organization separately.
Shared SLA's
20. 20
Service Delivery Models
Infrastructure as a Service (IaaS)
Platform as a Service (PaaS)
Software as a Service (Iaas)
21. 21
Service Delivery Models
Source: Cloud Computing Use Cases, a white paper produced by the Cloud Computing Use Case
Discussion Group, Version 2.0, 30 October 2009
22. 22
Services Delivery Models
Infrastructure as a Service (IaaS)
Consumer can utilize “Fundamental Computing
Resources” such as Processing Unit, Storage,
Networking and Operating System.
Consumer can control the operating system,
Storage, Application.
23. 23
IaaS Benefits
Low IT Capital Investment and on-going
operation Cost
Shorter delivery time and Fully scalable
Higher Level of Value-added services
Reduces Maintenance, Monitoring and
Management cost
Easy to Manage
24. 24
Services Categories
Platform as a Service (PaaS)
– Allows users to create their own cloud based
application using provider specific API's and/or
libraries.
25. 25
PaaS Benefits
Low Infrastructure & Lower Risk
Lightweight development IDE
Easy and quick deployment
Reusable code and business logic
Integration with other web services
Centralized information management
Secured and customized access
Easy Collaboration
26. 26
Services Categories
Software as a Service (SaaS)
– Consumers purchase the ability to access
and use an application or service that is
hosted in the cloud.
27. 27
SaaS Benefits
Shorter deployment time
Global Availability
Easier upgrades
Lower Initial costs
High Adoption
28. 28
Cloud Security
Claims Based Authentication
A trusted authority (Issuer) issues a signed
security
Token containing a set of claims (credentials) which is
given to the application for validation.
The application will authenticate the user if the
security token is valid and signed by a trusted issuer
29. 29
Cloud of the future is an ecosystem
Source: Cloud Computing Use Cases, a white paper produced by the Cloud Computing Use Case
Discussion Group, Version 2.0, 30 October 2009