Cloud 101

© 2009 Grid Dynamics — Proprietary and Confidential

CLOUD 101

Grid Dynamics

September, 2009

© 2009 Grid Dynamics — Proprietary and Confidential 2

EVOLUTION OF COMPUTING

9/18/09

Programming languages

abstract algorithms from machine instructions

1951 A0 SYSTEM1954 FORTRAN

Operating Systems

abstract software from hardware 1959 GM OS IBM7011965 OS/360

File Systems abstract data storage from physical medium

1961 DECTape

Databases abstractdata from physical storage 1960-xIDS,IMS1970 RDBMS

Networking protocols

abstract communication from network

1969 ARPANet

Virtual machines abstractapplication from platform 1995 JVM

Grid Computing abstractdistributed application from distributed platform

1990-2000

Cloud Computing Abstract application from infrastructure

2000-2009


CLOUD COMPUTING LIKE POWER GRID

9/18/09


WHY NOW?• Broadband networks

• Adoption of Software as a Service

• Gmail, Salesforce, Friendster, MySpace, etc…

• Web 2.0 mindset: user-generated data prevails

• Virtualization technologies for

commodity x86

• Virtual Machines and Virtual Appliances as a standard

deployment object

• Open Source software

• Community, Low entry barrier, No per-CPU costs

9/18/09


ANATOMY OF A CLOUD: SPI PARADIGM

• Building Blocks• Hardware infrastructure (IaaS)

• AWS, GoGrid, Rackspace, Mosso, Flexiscale

• Platform (PaaS)• Force.com, Google App Engine, Gmaps API

• Software (SaaS)• Salesforce.com, Gmail

• Cloud principles• Pay As You Go

• Self-service

• Programmable

• Dynamic provisioning

• Cloud scope• Public, Private, Hybrid

9/18/09


CLOUD COMPUTING IS NOT JUST

9/18/09

Shared instances

of application

s Clustered computing

HPC applications

Hosting infrastructur

e

Distributed computing

Web Hosting


CLOUD COMPUTING IS ALSO• Cloud platform services

• Storage and Data Services

• Scalable archiving and backup solution

• Relational, Object or Column Databases

• Network-attachable block storage

• Messaging

• Other: Auth, CDN, URI fetching, Task Scheduling, Image Processing, etc.

• Cloud middleware• Grid Computing Middleware

• Data grids

• Provisioning systems

• Cloud API• Monitoring

• Management

• Orchestration

9/18/09

CloudAPI

Middle-ware

Platform

services


WHAT IS A CLOUD APPLICATION?• Horizontally scalable

• Performance can be increased dynamically by the means of adding CPU

boxes and/or storage resources

• Failure resistant

• Features failover and failback on application level

• Manages persistence on application level

• Cloud aware

• Relies on cloud services

• Relies on application specific monitoring as well as to Cloud API to

monitor and manage resources

• Not so security critical9/18/09


NATIVE CLOUD APPLICATION PRINCIPLES• Massively parallel by design

• Keep state in data grid

• Process in computation grid

• Load balance

• On-demand elastic scalability• Elastic scalability to scale not only up but also

down with workload

• Use SLA to define scaling needs

• Use Cloud API to satisfy scaling needs

• Loosely coupled• Component-based

• Wrap cloud API and Cloud Services to avoid lock-in

• Resilient by design• Failover and failback features to withstand resource

failure

• Cloud API is used to restore/re-provision failed resource

9/18/09


CLOUD SCOPE: PUBLIC, PRIVATE, HYBRID• Public Clouds

• Out there, provided as a service

• VM-Image-based or Virtual Private Datacenter-based

• Really massively scalable

• Private Clouds• Benefits of public clouds, but:

• Internal bandwidth for access cloud resources

• Maintain control over resources

• Meet enterprise/legal regulations

• Hybrid Clouds• Augment private cloud with capacity of public cloud (cloud bursting)

• Suitable for handling traffic spikes or periodic massive computation jobs

• Introduce complexity of managing application on private-public boundaries, especially wrt data transfer

9/18/09


BENEFITS OF CLOUD COMPUTING

• Benefits of scale• Large cloud provider can always invest more into robust cloud services

than you

• Illusion of “infinite capacity” for processing and storage resources

• Bursting: Employ large amount of servers with ease

• Risk management• Most infrastructure risks moved to cloud provider (HW and network

failures is provider’s problem)

• Resilient and redundant cloud services as building blocks

• Opportunity to automate failover and failback

• Speed of innovation• Low entry cost for innovative programs

• Easy to try a lots of ideas and not meet IT-related bounds

9/18/09


WHEN IT RAINS: CLOUD CHALLENGES• Raw performance

• Virtualization tolls CPU and I/O

• Data-compute affinity• Moving data in and out is costly

• Firm SLA• Fair share of resources is not

guaranteed in all scenarios

• Opacity• Reliability and safety

technologies are proprietary and unknown

• Security and Data privacy• Cloud abstracts out where actual

data processing occurs

• Digital Millennium Copyright Act

(DCMA) and CryptoExport laws

• Lock-In• No standards so far

• Legacy as a Service• Rarely cloud-friendly

• Deployment• Automate, automate, automate

• Everything fails all the time• Cloud provider outages, hidden

and obvious

• Unexpected Cloud API and Services evolution

9/18/09


CLOUD EVOLUTION

• Standards• AWS standard de-facto, GoGrid API, Sun API: need to

converge

• Infrastructure• More tooling, monitoring and management

• Computing• Inter-cloud portability (VM migration)

• PaaS with more platforms support: Python, Java, Ruby, etc..

• Storage• Block and Keyed storage evolution

• Non-SQL data sources for OLAP and OLTP

• APIs• Generic and domain specific open APIs

9/18/09

© 2009 Grid Dynamics — Proprietary and Confidential

Thank You!

Eugene Steinberg,

CTO

Technology

Cloud 101