Differences between Virtualization and Cloud

Cloud &
Virtualization
Duan van der Westhuizen
Private Cloud Product

A Difference in Philosophy and Approach

Virtualization Cloud
Not elastic compute or Holistic approach to
elastic storage – solves for infrastructure automation
server consolidation
Key drivers are agility and
Key driver are consolidation and automation, Capex to Opex
resource optimization and scalability

Supports standard application Applications built to elastically
architecture. VM functions scale in Cloud via API integration
logically as traditional server.
Apps built to scale Horizontally
Apps Scale vertically by adding on commodity hardware
more resources CPU, RAM, etc.

RACKSPACE® HOSTING | WWW.RACKSPACE.COM
2

Architectural Differences - An Analogy



Architectural Differences - An Analogy

Shared resources approach Shared-Nothing Architecture
(Sharding)
Central controller
Each node is independent
Nodes cannot do anything without and self-sufficient
reporting to the “hub”
No single point of contention
Single point of contention across the system
Limited scalability
Scale to thousands by simply
adding cheap commodity hardware


APP LAYER
• Scaling and Redundancy: The
Different Approaches

• Stateful vs. Stateless
Applications

• Why Should You Care?


THE 1ST RULE OF CLOUD
Redundancy
in the App…

not the
INFRASTRUCTURE


Redundancy in
Virtualization
• Clustered hypervisors for high availability

• Live migration technology for fault tolerance

• Multiple levels of redundancy through backup
hardware components


Vertical Scaling
• Larger equals more performance output, limit to
scale you can attain

• Multiple backup systems in infrastructure
enable redundancy


Horizontal Scaling
• Add smaller inexpensive nodes to increase
overall output. No limit to scalability

• One dies, simply replace with another


What Does This Mean for Apps?

Vertical Scaling
Add more RAM or move workload to Horizontal Scaling
server with faster CPU to increase Add more nodes and share the load,
performance delete them when you’re done


Application State

It’s like a phone call to your
Insurance provider…

“Stateful”
All your info is recorded by the
operator, the call drops, you call
back and you carry on where you
left off. No interruption.

“Stateless”
You spend the call relaying the
information, the call drops. When
you call back you have to repeat it
all again. No history of connection.


APPLICATION STATE

• Servers are static, therefore • Cloud environments are not
application state can be effectively inherently redundant. Applications
should be architected for redundancy.
managed on single server

• Cloud servers can be created and
• No spin up and tear down effect deleted dynamically
creating state issues
• Applications need to be architected
• Infrastructure such as load to manage state, otherwise users will
balancer can be used to manage not have a seamless experience
stateful connections


Finding the Best Fit

Virtualized Apps Cloud Apps
• Corporate Payroll Systems • Big Data platforms
• ERP Systems • Social Media
• Traditional Ecommerce Platforms
Apps • Streaming Media
• Office Collaboration • Web 2.0


Differences between Virtualization and Cloud

More Related Content

What's hot

Viewers also liked

Similar to Differences between Virtualization and Cloud

Recently uploaded

Differences between Virtualization and Cloud