esteban kolsky

thinkJar “cloud purist” @ekolsky

first mention ever of cloud computing model?

first mention ever of cloud computing model?

1906

distributedcomputing

1931

gridcomputing

1970s

network isthe computer

1984

CORBADCOM

1990s

networkcomputing

1999

cloudcomputing

2004

state of sirocco

2007

evolution of the cloud

sirocco: a windstorm that lifts up clouds of dust and sand(similar to a hadoop)

defining the cloud by “the book”cloud computing is the delivery of computing as a service rather than a product, whereby shared resources, software, and information are provided to computers and other devices as a utility (like the electricity grid) over a network (typically the internet)

wikipedia

defining the cloud by “the book”cloud computing is the delivery of computing as a service rather than a product, whereby shared resources, software, and information are provided to computers and other devices as a utility (like the electricity grid) over a network (typically the internet)

wikipediaHIGH LEVEL

defining the cloud by “the book”cloud computing is the delivery of computing as a service rather than a product, whereby shared resources, software, and information are provided to computers and other devices as a utility (like the electricity grid) over a network (typically the internet)

wikipedia

cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction

NIST

HIGH LEVEL

defining the cloud by “the book”cloud computing is the delivery of computing as a service rather than a product, whereby shared resources, software, and information are provided to computers and other devices as a utility (like the electricity grid) over a network (typically the internet)

wikipedia

cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction

NISTTACTICAL

HIGH LEVEL

defining the cloud, the “purist” way

• leverage, mashup parts of history, current definitions– distributed computing– single instance with replication– uses systems management– computing as a service– separation into three layers– open network– connected and integrated– measured by the usage, not by the user– public, public, and public

IaaS

PaaS

SaaS

S

S

S

S

P

P

P P

I

I

I

I

connectivitydatabaselegacyinternet

securitybusiness rulescompliancedirectory

presentationvalidationinteractionpersonalization

a picture worth a thousand words or more

barriers to cloud – irrational fear of the unknown

barriers to cloud – change management

barriers to cloud –three laughable IT excuses

integrationscalability

security

barriers to cloud –three laughable IT excuses

debunking security in the cloud: problem

system 1 sys 2 sys 3

partner vendor

system x

debunking security in the cloud: solution

SPI

SPI

SPI

SPI

SPI

SPI

security service

security token, created and managed by PaaS

debunking integration: problem

system 1

system 2

system 3

partner vendor

system x

debunking integration: solution a

S

PI

S

PI

S

PI

S

PI

SaaS-SaaS integration, within the application, leveraging

the cloudsimilar to existing, uses

service calls, middleware

debunking integration: solution b

S

PI S

PI

S

PI

S

PIPaaS-PaaS integration,

leveraging the cloud, no need for middleware,easiest for elasticity (scale out), establish once, reuse many times as necessary

scalability: three sustaining pillars

design for scalability

in the cloud

scalability must occur

in two ways – up

and out

define scalability by

CapacityAvailabilityPerformance

cloud scalability

the entire concept of cloud computing was conceived for scalability sake

making the case for cloud computing E1

making the case for cloud computing E1

conomicseasiest part of the equation: someone else hosts hardware, software,

maintenance

anyway to look at it, remote, distributed computing is cheaper

move from CAPEX to OPEX is very attractive to managing stakeholders

cloud ROI traditionally done by comparing IT budgets to cloud expenses

#mmmkay

scalability, integration are cheaper and easier, security is still under (hot)

debate

making the case for cloud computing E2

making the case for cloud computing E2

lasticity

inherent to cloud architectures

makes case for scalability, high-availability, failover planning

done wrong – remember the failure of amazon EC2 and the

problems it caused

is a scale-out model in single-tenancy, multi-instance, that cannot be

tested

requires systems management for proper instance maintenance

making the case for cloud computing E3

making the case for cloud computing E3

nterprise application stores

mobile, social, user empowerment – all changed the game

users aren’t putting up with big, complex applications – they want “apps” on

iPad

best bet for support for all business is adoption of EAS, cloud is a must for that

model scalability, flexible interfaces, myriad device access via platform – all

part of the cloud two-to-three year trend, if you haven’t started – better get

going

making the case for cloud computing E4

making the case for cloud computing E4

xpansion

plans for all business units in next few years include “cloud” and SaaS

plans for IT over next three-to-four years include cloud infrastructure

integration, plans from partners, providers, suppliers, associates include cloud

in next five years

expansion of any organization must include cloud going forward, no questions

if all other fails, cite the fact that competitors are expanding into cloud

#Winning

making the case for cloud computing E5

making the case for cloud computing E5

volution

evolution of the world comes down to cloud, organizations have to adapt

vendors are evolving their products from hosted, on-demand to cloud

ventures with partners, other organizations will demand cloud; three-to-four

years

customers are demanding cloud –stirred up by microsoft “to the cloud” TV ads

with differentiation of what is cloud and how to deploy in it, definitely a must-

do

making the case for cloud computing E6

making the case for cloud computing E6

infrastructurreports say from 10% to 30% of IT budgets put on cloud infrastructure

reports highlight more money spent by BU than IT on SaaS applications;

continuing

organizations cannot leverage the cloud as an external service only, must

integrate

to make cloud work across organization, to retain security, to enhance

integration – IT must be responsible for centralized cloud infrastructure; CEOs

are seeing this

issues: hosted != on-demand != cloud• hosted: a vendor puts a web-interface to their apps

– MT (multitenancy) is a big deal here– licensing is by the user, as usual– reduced functionality or poor performance by comparison

• on-demand: vendors leverages SaaS, PaaS model– web interface– MT benefits vendor; not so much clients– usually SaaS and PaaS “all in one” failing to leverage cloud

• cloud: three layer distributed computing model– MT, single-instance hard to scale; ST, multi-instance better– licensing by usage, starting, is winner model for biz

issues: private cloud• short, simple, sweet

• today’s private cloud is used as a bridge between client-server, web-based, on-demand, and SaaS worlds to get to the real cloud infrastructure

• use if you must, you are better off planning around it

any well done definition of the cloud specificallycalls for open networks to support the cloud;private clouds violate core tenet of cloud

your next steps

• define the cloud (for you)• take charge of your existing “cloud” initiatives

– across stakeholders– make case for central IT control

• setup 3-5 years strategy and investment• get going, do your infrastructure while you

leverage SaaS and on demand solutions• learn, implement, learn, implement – you get the

idea

let’s talk…