Sie sind auf Seite 1von 15
   
     
 

ENTERPRISE CLOUD ADOPTION FRAMEWORK

ECAF

STANDARDIZATION AS THE ROAD TO

 

ENTERPRISE CLOUD

   

CLOUD CHANGES EVERYTHING

The$IT$industry$has$weathered$its$share$of$architectural$fads$that$have$entered$and$exited$data$center$

fashion$like$the$length$of$hemlines.$It’s$no$wonder$so$many$of$us$have$grown$cynical$about$each$subse<

quent$architectural$shift$that$promises$to$change$the$world.

Of$course,$cloud$computing$hasn’t$let$us$down$when$it$comes$to$hype.$Very$few$IT$trends$have$delivered$

quite$its$degree$of$vendor$bluster$and$grand$pronouncement.$(And$that’s$saying$something!)

But$while$widespread$“cloud<washing”$may$test$our$patience$for$vendor$hyperbole,$it$shouldn’t$detract$(or$

distract)$from$the$fundamental$truth$that$cloud$is$perhaps$the$most$important$architectural$trend$of$our$

generation—and$certainly$no$temporary$fad.

The$truth$is$(if$you’ll$pardon$the$bluster)$cloud$does$change$everything.$It$turns$the$traditional$IT$operating$

model$on$its$ear,$enabling$enterprises$and$service$providers$to$become$far$more$responsive$to$changing$

demand$patterns.$Deep$automation$means$that$infrastructure$and$platforms$can$be$provisioned$and$de<

provisioned,$scaled$and$de<scaled$on$demand.$

Infrastructure$as$a$service$takes$the$time$and$effort$out$of$provisioning$hardware$capacity:$

With Infrastructure as a service (IaaS)

CLOUD CHANGES EVERYTHING The$IT$industry$has$weathered$its$share$of$architectural$fads$that$have$entered$and$exited$data$center$ fashion$like$the$length$of$hemlines.$It’s$no$wonder$so$many$of$us$have$grown$cynical$about$each$subse< quent$architectural$shift$that$promises$to$change$the$world. Of$course,$cloud$computing$hasn’t$let$us$down$when$it$comes$to$hype.$Very$few$IT$trends$have$delivered$ quite$its$degree$of$vendor$bluster$and$grand$pronouncement.$(And$that’s$saying$something!) But$while$widespread$“cloud<washing”$may$test$our$patience$for$vendor$hyperbole,$it$shouldn’t$detract$(or$ distract)$from$the$fundamental$truth$that$cloud$is$perhaps$the$most$important$architectural$trend$of$our$ generation—and$certainly$no$temporary$fad. The$truth$is$(if$you’ll$pardon$the$bluster)$cloud$does$change$everything.$It$turns$the$traditional$IT$operating$ model$on$its$ear,$enabling$enterprises$and$service$providers$to$become$far$more$responsive$to$changing$ demand$patterns.$Deep$automation$means$that$infrastructure$and$platforms$can$be$provisioned$and$de< provisioned,$scaled$and$de<scaled$on$demand.$ Infrastructure$as$a$service$takes$the$time$and$effort$out$of$provisioning$hardware$capacity:$

Platform$as$a$service$completes$the$picture$by$automating$operating$systems$and$middleware:

With Platform as a service (PaaS)

CLOUD CHANGES EVERYTHING The$IT$industry$has$weathered$its$share$of$architectural$fads$that$have$entered$and$exited$data$center$ fashion$like$the$length$of$hemlines.$It’s$no$wonder$so$many$of$us$have$grown$cynical$about$each$subse< quent$architectural$shift$that$promises$to$change$the$world. Of$course,$cloud$computing$hasn’t$let$us$down$when$it$comes$to$hype.$Very$few$IT$trends$have$delivered$ quite$its$degree$of$vendor$bluster$and$grand$pronouncement.$(And$that’s$saying$something!) But$while$widespread$“cloud<washing”$may$test$our$patience$for$vendor$hyperbole,$it$shouldn’t$detract$(or$ distract)$from$the$fundamental$truth$that$cloud$is$perhaps$the$most$important$architectural$trend$of$our$ generation—and$certainly$no$temporary$fad. The$truth$is$(if$you’ll$pardon$the$bluster)$cloud$does$change$everything.$It$turns$the$traditional$IT$operating$ model$on$its$ear,$enabling$enterprises$and$service$providers$to$become$far$more$responsive$to$changing$ demand$patterns.$Deep$automation$means$that$infrastructure$and$platforms$can$be$provisioned$and$de< provisioned,$scaled$and$de<scaled$on$demand.$ Infrastructure$as$a$service$takes$the$time$and$effort$out$of$provisioning$hardware$capacity:$

This$translates$to$far$better$responsiveness$through$an$agile$and$adaptive$operating$model.$But$every$bit$

as$important$is$cloud’s$impact$on$the$economic$model$for$IT:$Commoditization$and$better$utilization$of$in<

frastructure$means$you$spend$less—and$elastic,$pay<as<you<go$pricing$models$means$spending$is$closely$

aligned$to$need.

WHY DOES CLOUD NEED AN ADOPTION MODEL, ANYWAY?

A$fundamentally$new$operating$model$means$a$fundamentally$new$approach$to$how$IT$services$are$de<

signed,$delivered$and$maintained.$Cloud$dictates$substantial$architectural$change.

Today,$enterprise$IT$and$managed$service$providers$are$under$pressure$to$accelerate$their$own$cloud$

transformations$in$a$race$to$attract$and$retain$customers.$But$the$reality$is$that,$despite$the$massive$invest<

ments$that$have$been$ploughed$into$cloud$projects,$it’s$a$nascent$landscape$with$very$few$patterns$and$

precedents$that$you$can$rely$on$to$assure$success.$

what$really$matters.$We’re$bombarded$by$layers$and$layers$of$cloud<driven$change$that$leave$us$paralyzed$

in$the$face$of$it$all.$How$do$you$assess$the$relative$priority$of$self<service$catalogs,$chargeback,$showback,$

resource$management,$new$app$platforms,$compliance,$security,$etc.?$The$list$goes$on.

That’s$why$we$believe$cloud$builders$need$an$adoption$model$for$thinking$through$the$graduated$set$of$

investments$required$to$execute$a$cloud$transformation.$

This$is$the$role$of$the$Enterprise)Cloud)Adoption)Framework—to$help$enterprise$IT$and$managed$service$

providers$understand$the$starting$points,$traps$and$destinations$on$the$journey$to$cloud.$It’s$designed$to$

shine$light$on$the$paths,$providing$the$guideposts$for$making$decisions$and$thinking$through$options$and$

alternatives.$To$borrow$an$investor’s$word,$it’s$designed$to$“de<risk”$your$cloud$project$and$to$assure$better$

outcomes.

Forging$ahead$without$this$sort$of$framework$may$lead$to$false$starts$and$missteps$that$slow$your$cloud$

transformation,$introducing$competitive$risks$and$diminished$credibility.$Like$any$other$architectural$trans<

formation,$it’s$absolutely$essential$to$begin$with$the$end$in$mind—and$with$a$detailed$understanding$of$the$

sequence$and$implications$of$each$successive$investment.$

WHO ARE WE TO PRESCRIBE AN ADOPTION MODEL?

In$the$early$dawn$hours$of$the$cloud$journey$nobody$can$credibly$claim$absolute$authority$on$this$subject.$

But$the$group$behind$this$framework$has$combined$experience$that$rivals$any$other$group$of$professed$

cloud$experts$today.

Here’s$some$color$on$its$authors:

Above$all,$we’re$informed$and$disciplined$pragmatists$who$favor$solutions$that$yield$real$business$out<

In$addition,$we’re$committed$disciples$of$application<centric$practices.$We$believe$that$IT$should$be$about$

apps,$not$infrastructure.$Our$goal$is$to$shine$light$on$the$pathways$for$making$IT$organizations$truly$appli<

cation$centric$by$automating$and$abstracting$infrastructure$and$platforms.

< enced$by$our$pragmatic$philosophies$toward$cloud$transformations.$We$believe$it$will$help$you$set$the$right$

are$not$ready$for$prime$time$and$those$that,$propped$up$by$hype,$project$the$appearance$of$a$silver<bullet$

solution$to$all$of$your$cloud$requirements.

Remember:$In$cloud$transformations,$there$are$no$silver$bullets.$Beware$of$those$who$advise$you$other<

wise.$Cloud$is$a$change$management$exercise$and$enterprises$are$highly$complex$entities.

Thus,$the$Enterprise$Cloud$Adoption$Framework.

ASSUMPTIONS AND PARAMETERS

Before$we$introduce$the$Enterprise$Cloud$Adoption$Framework,$it’s$important$to$clarify$our$intent$by$stating$

what$this$model$is—and$what$it$isn’t—and$what$ground$it$attempts$to$cover.

This$framework$is$designed$for$cloud$builders—both$enterprise$IT$organizations$and$managed$service$

providers—who$seek$to$evolve$their$traditional$data$center$environments$into$large<scale$clouds.$

It$covers$infrastructure—compute,$network$and$storageW$and$it$covers$platforms—operating$systems,$

middleware$and$other$software$that$enables$applications.$

In$the$cloud$vernacular,$the$framework$explores$the$infrastructure<as<a<service$(IaaS)$and$platform<as<a<

service$(PaaS)$layers$of$the$stack,$but$it$excludes$software$as$a$service$(SaaS).$

It’s$worth$explaining$why!$

We’re$big$believers$in$SaaS$and$suggest$that$it$should$be$high$on$your$list$of$options$for$off<the<shelf$ap<

plications$that$serve$general<purpose$business$requirements.$If$you’re$looking$for$guidance$as$a$consumer$

of$SaaS$applications,$this$is$the$wrong$resource$for$you.$

provider—you’ve$come$to$the$right$place.$This$framework$can$help$you.

In$general,$the$Enterprise$Cloud$Adoption$Framework$is$designed$to$guide$you$through$the$cloud$transfor<

mation$of$infrastructure$and$platforms$that$enable$applications.$These$applications$can$be$custom$one<offs$

that$serve$the$needs$of$a$small,$but$valued$user$community,$or$general<purpose$SaaS$applications$that$

serve$the$needs$of$very$large$populations$of$users.

So,$let’s$take$a$look$at$the$Enterprise$Cloud$Adoption$Framework.$

ENTERPRISE CLOUD ADOPTION FRAMEWORK

The$Enterprise$Cloud$Adoption$Framework$examines$infrastructure$and$platforms,$which$are$well$under<

stood$as$the$foundations$for$the$traditional$data$center,$but$must$change$dramatically$in$the$face$of$a$cloud$

transformation.$

In$this$context,$infrastructure$refers$to$the$compute,$network$and$storage$resources$that$are$the$physical$

substrate$for$software$systems.$Platform$refers$to$the$software$that$supports$applications$such$as$operat<

ing$systems,$app$and$web$servers,$databases$and$other$middleware.$

A$fundamental$premise$of$the$Enterprise$Cloud$Adoption$Framework$is$the$notion$of$standardization.$Be<

standardization$as$a$strategic$driver$in$IT.$

WHY STANDARDIZATION MATTERS

For$all$the$discussion,$debate$and$commentary$on$the$cloud$transformation,$there$has$been$scarcely$little$

analysis$of$the$role$of$standardization.$

It’s$our$strong$belief$that$standardiza< tion$is$the$primary$driver$for$all$of$the$ < ing.$Standardization$is$utterly$essential$ to$the$cloud$operating$model.$This$

at$every$aspect$of$cloud$through$the$

lens$of$standardization.$

The$idea$of$standardization$strikes$

most$IT$professionals$like$motherhood$

WHY STANDARDIZATION MATTERS For$all$the$discussion,$debate$and$commentary$on$the$cloud$transformation,$there$has$been$scarcely$little$ analysis$of$the$role$of$standardization.$ It’s$our$strong$belief$that$standardiza< tion$is$the$primary$driver$for$all$of$the$ < ing.$Standardization$is$utterly$essential$ to$the$cloud$operating$model.$This$ at$every$aspect$of$cloud$through$the$ lens$of$standardization.$ The$idea$of$standardization$strikes$ most$IT$professionals$like$motherhood$ and$apple$pie—what’s$not$to$like?$But$we$believe$there’s$a$deeper$story$here—a$story$that$affects$the$ decisions$we$make$in$undertaking$a$cloud$transformation.

and$apple$pie—what’s$not$to$like?$But$we$believe$there’s$a$deeper$story$here—a$story$that$affects$the$

decisions$we$make$in$undertaking$a$cloud$transformation.

Industrial$and$scale$manufacturing$

operations$offer$lessons$about$

standardization$that$are$useful$to$

enterprise$IT$organizations.$Here,$the$drive$toward$standardization$in$parts,$process$and$policy$is$essential$

for$accelerating$production$cycles,$driving$down$costs$and$increasing$quality.$

Standardization$is$also$a$critical$enabler$for$automation—and$automation$is$a$critical$enabler$for$clouds.$

why$some$degree$of$standardization$is$a$precondition$for$automation—which$is$a$precondition$for$cloud.

< nently$in$your$future.

But$for$complex$enterprise$environments,$the$answer$isn’t$as$simple$as$a$rush$to$full$standardization.$Stan<

It’s$useful$to$think$of$standardization$as$a$lever$that$follows$a$continuum$of$extreme)diversity$on$one$pole$

and$extreme)uniformity$on$the$other.$

<

forcing$customers$into$a$prescribed$solution.

< tion$isn’t$always$the$right$answer$for$today’s$complex$enterprise$environments.$

In$fact,$the$level$of$standardization$that$makes$sense$for$most$organizations$resembles$a$sort$of$Goldi<

locks$logic:$Not$too$much.$Not$too$little.$

What’s)just)

STANDARDIZING YOUR INFRASTRUCTURE

Historically,$most$enterprise$IT$organizations$have$been$like$custom$builders,$where$customer$needs$are$

adds$substantial$cost,$time$and$risk$to$procurement,$provisioning,$maintenance$and$support.$$

The$cloud$transformation$forces$us$to$clean$up$this$mess.

You$may$think$of$the$spectrum$of$infrastructure$standardization$

as$the$following:

Diverse — Infrastructure$resources$are$fragmented$and$ non<standard,$which$addresses$the$varied$requirements$

Standard —$Infrastructure$resources$are$pooled$across$ departments$and$user$communities$to$improve$utilization$ and$economies$of$scale.

Elastic —$Infrastructure$is$pooled$and$further$standard< ized$as$a$set$of$T<shirt<sized$options$(e.g.,$small,$medium$ and$large)$with$corresponding$pricing,$service$levels,$etc.$

< forcing$customers$into$a$prescribed$solution. < tion$isn’t$always$the$right$answer$for$today’s$complex$enterprise$environments.$ In$fact,$the$level$of$standardization$that$makes$sense$for$most$organizations$resembles$a$sort$of$Goldi< locks$logic:$Not$too$much.$Not$too$little.$ What’s )just) STANDARDIZING YOUR INFRASTRUCTURE Historically,$most$enterprise$IT$organizations$have$been$like$custom$builders,$where$customer$needs$are$ adds$substantial$cost,$time$and$risk$to$procurement,$provisioning,$maintenance$and$support.$$ The$cloud$transformation$forces$us$to$clean$up$this$mess. You$may$think$of$the$spectrum$of$infrastructure$standardization$

< sive.$

STANDARDIZING YOUR PLATFORMS

We$tend$to$think$of$IT$as$infrastructure—heavy$things$you$can$drop$on$your$foot—but$that’s$an$incomplete$

picture.$The$reality$is$that$infrastructure$is$only$valuable$(and$valued)$to$the$extent$that$it$enables$applica<

That’s$why$a$cloud$transformation$isn’t$complete$until$it$addresses$the$full$scope$of$resources$required$to$

stand$up$applications.$These$resources$include$operating$systems,$databases,$web$servers,$application$

servers,$application$frameworks,$data$access$and$integration$tools$and$other$middleware$that$enables$ap<

plications.

Thus,$in$addition$to$infrastructure,$a$cloud$transformation$must$also$address$software$platforms.$

In$similar$fashion,$your$drive$to$platform$standardization$follows$three$stages:

Diverse —$Custom$platforms$are$ assembled$as$one<offs$to$meet$the$ < plications.$This$is$slow$and$costly$to$ maintain$and$support.

Standard —$Platforms$are$consoli<

< sive.$ STANDARDIZING YOUR PLATFORMS We$tend$to$think$of$IT$as$infrastructure—heavy$things$you$can$drop$on$your$foot—but$that’s$an$incomplete$ picture.$The$reality$is$that$infrastructure$is$only$valuable$(and$valued)$to$the$extent$that$it$enables$applica< That’s$why$a$cloud$transformation$isn’t$complete$until$it$addresses$the$full$scope$of$resources$required$to$ stand$up$applications.$These$resources$include$operating$systems,$databases,$web$servers,$application$ servers,$application$frameworks,$data$access$and$integration$tools$and$other$middleware$that$enables$ap< plications. Thus,$in$addition$to$infrastructure,$a$cloud$transformation$must$also$address$software$platforms.$ In$similar$fashion,$your$drive$to$platform$standardization$follows$three$stages: Diverse —

for$automation.

Elastic —

abstract$the$complexity$of$infrastructure$and$platforms,$so$developers$can$focus$on$what$customers$care$

about:$Applications.

As$we’ll$discuss$in$the$next$section,$PaaS$is$absolutely$the$correct$goal$for$your$cloud$transformation,$but$

today$it$doesn’t$match$up$to$the$complex$realities$of$enterprise$IT.$

Again,$the$choices$you$make$about$standardization$are$compromises$between$tradeoffs.$Let’s$take$a$

closer$look$at$these$tradeoffs$to$inform$the$strategy$you$set$on$your$path$to$cloud$transformation.

PUTTING IT ALL TOGETHER

Now$that$we$have$a$map$for$the$landscape$of$standardization,$let’s$explore$some$of$its$more$popular$desti<

nations.$These$areas$of$the$map$represent$common$patterns—and$anti<patterns—for$cloud$adoption.$

SNOWFLAKE SYSTEMS

$

When$both$infrastructure$and$app$platforms$are$diverse,$we$have$the$traditional$IT$world$of$delivering$and$ < ments,$because$IT$focuses$on$serving$the$precise$needs$of$individual$application$customers.$The$organi< zation$itself$is$often$decentralized$and$divided$into$app$support$teams.

cloudify$it.”

about:$Applications. As$we’ll$discuss$in$the$next$section,$PaaS$is$absolutely$the$correct$goal$for$your$cloud$transformation,$but$ today$it$doesn’t$match$up$to$the$complex$realities$of$enterprise$IT.$ Again,$the$choices$you$make$about$standardization$are$compromises$between$tradeoffs.$Let’s$take$a$ closer$look$at$these$tradeoffs$to$inform$the$strategy$you$set$on$your$path$to$cloud$transformation. PUTTING IT ALL TOGETHER Now$that$we$have$a$map$for$the$landscape$of$standardization,$let’s$explore$some$of$its$more$popular$desti< nations.$These$areas$of$the$map$represent$common$patterns—and$anti<patterns—for$cloud$adoption.$ SNOWFLAKE SYSTEMS $ When$both$infrastructure$and$app$platforms$are$diverse,$we$have$the$traditional$IT$world$of$delivering$and$ <

VM

SPRAWL

$

< tion$and$sprawling$virtualization?$The$stock$answer$is$governance.$Sprawl$means$hordes$of$unnecessary,$

<

even$more$systems$than$before.$

$ < tion$and$sprawling$virtualization?$The$stock$answer$is$governance.$Sprawl$means$hordes$of$unnecessary,$ < even$more$systems$than$before.$ CLOUD SPRAWL Amazon$(and$expense$it$as$a$book$purchase!). The$result$is$cloud$sprawl.$ IaaS$is$ideal$infrastructure,$but$IaaS$alone$cannot$move$the$needle$on$app$delivery.$Even$in$a$full<blown$ 9

CLOUD

SPRAWL

Amazon$(and$expense$it$as$a$book$purchase!).

The$result$is$cloud$sprawl.$

IaaS$is$ideal$infrastructure,$but$IaaS$alone$cannot$move$the$needle$on$app$delivery.$Even$in$a$full<blown$

error<prone$as$ever.

That$rounds$out$the$bottom$row$of$our$matrix.$Regardless$of$infrastructure$choice,$app$delivery$is$ham<

strung$when$app$platforms$are$diverse.$At$the$opposite$end$of$the$spectrum,$what$can$full$platform$stan<

dardization$do$for$IT?

error<prone$as$ever. That$rounds$out$the$bottom$row$of$our$matrix.$Regardless$of$infrastructure$choice,$app$delivery$is$ham< strung$when$app$platforms$are$diverse.$At$the$opposite$end$of$the$spectrum,$what$can$full$platform$stan< dardization$do$for$IT? ELASTIC PAAS When$app$platforms$and$underlying$infrastructure$are$both$highly$standardized,$we$have$elastic$PaaS,$ which$many$vendors$simply$call$PaaS.$With$elastic$PaaS,$you$write$applications$to$a$strict,$consistent$ platform$API.$That$level$of$standardization$makes$it$possible$to$safely$run$any$number$of$totally$unrelated$ apps$on$the$same,$shared$platform$instance.$And$as$we$see$with$public$and$private$PaaS$offerings$such$ underlying$resource$utilization. enterprise$application$projects,$and$the$current$elastic$PaaS$offerings,$simply$aren’t$ready$for$each$other.$ The$biggest$problem$is$that$real$apps$require$tweaks$and$nonstandard$extensions$to$their$platforms—ev< erything$from$native$code$extensions$to$multiple$simultaneous$versions$of$the$same$platform<to<platform$ source<code$changes. <

ELASTIC PAAS

When$app$platforms$and$underlying$infrastructure$are$both$highly$standardized,$we$have$elastic$PaaS,$

which$many$vendors$simply$call$PaaS.$With$elastic$PaaS,$you$write$applications$to$a$strict,$consistent$

platform$API.$That$level$of$standardization$makes$it$possible$to$safely$run$any$number$of$totally$unrelated$

apps$on$the$same,$shared$platform$instance.$And$as$we$see$with$public$and$private$PaaS$offerings$such$

underlying$resource$utilization.

enterprise$application$projects,$and$the$current$elastic$PaaS$offerings,$simply$aren’t$ready$for$each$other.$

The$biggest$problem$is$that$real$apps$require$tweaks$and$nonstandard$extensions$to$their$platforms—ev<

erything$from$native$code$extensions$to$multiple$simultaneous$versions$of$the$same$platform<to<platform$

source<code$changes.

< < tecting$your$apps. Elastic$PaaS$is$ideal$for$next<generation$app$projects,$but$it’s$simply$too$strict$for$modern$enterprise$apps.

ENTERE PRISE PAAS
ENTERE
PRISE
PAAS

$

Enterprise$PaaS$means$on<demand,$standardized$app$platforms$for$the$current$generation$of$enterprise$ < pect—so$Enterprise$PaaS$is$based$on$self<service,$orchestrated$IaaS.$

< nately,$there’s$a$happy$compromise:$platform$stacks$on$demand.

With$Enterprise$PaaS,$IT$can$run$many$platform$instances$to$serve$the$distinct$needs$of$different$apps$and$

repeatable$stacks,$making$rapid$deploy$and$update$possible$without$app$rewrites.

We$believe$that$Enterprise$PaaS$is$simply$the$best$available$strategy$for$contemporary$enterprise$apps.

ENTERE PRISE PAAS $ Enterprise$PaaS$means$on<demand,$standardized$app$platforms$for$the$current$generation$of$enterprise$ < pect—so$Enterprise$PaaS$is$based$on$self<service,$orchestrated$IaaS.$ < nately,$there’s$a$happy$compromise:$platform$stacks$on$demand. With$Enterprise$PaaS,$IT$can$run$many$platform$instances$to$serve$the$distinct$needs$of$different$apps$and$ repeatable$stacks,$making$rapid$deploy$and$update$possible$without$app$rewrites. We$believe$that$Enterprise$PaaS$is$simply$the$best$available$strategy$for$contemporary$enterprise$apps. 11

ITEDRIVEN ENTERPRISE PAAS

What$about$standard$platforms$on$standard,$but$not$elastic,$infrastructure?$This$combination$makes$sense$

highly$tuned$infrastructure$requirements.$Just$as$elastic$app$platforms$are$too$standardized$for$today’s$

apps,$elastic$infrastructure$can$be$too$standardized$for$some$apps.$

RECOMMENDATIONS AND NEXT STEPS

So$how$can$the$Enterprise$Cloud$Adoption$Framework$actually$help$IT$chart$a$course$for$your$cloud$trans<

formation$aimed$directly$at$improved$business$outcomes?

< tive$development$and$for$next<generation$applications.

For$truly$static,$legacy$apps,$we$suggest$that$cloud$migration$is$not$particularly$helpful.$Beyond$the$well<

agile,$on<demand$platforms$or$infrastructure$for$apps$that$never$change.

For$next<generation$application$plans,$elastic$PaaS$is$clearly$a$winner.$By$the$time$your$next<generation$

initiatives$are$ready$to$implement,$the$PaaS$platforms$you$need$are$likely$to$be$ready.

The$interesting$question$is$what$to$do$for$the$vast$middle$of$enterprise$apps—that$mass$of$code$in$Java$

and$.NET$for$mainstream$middleware$platforms.$Here$are$our$recommendations.

RECOMMENDATION 1:

DON’T ADOPT CLOUD WITHOUT EXPLICIT INTENT TO STANDARDIZE

more$than$technology.$It$needs$the$will$and$the$ability$to$standardize.$

Standardization$must$become$an$initiative,$not$just$a$side$effect$of$cloud.

<

patterns.$And$use$patterns$are$hard$to$standardize$with$pre<cloud$technology.$It’s$a$completely$symbiotic$

relationship.

Standardization$and$cloud$reinforce$each$other$and$rise$together.$If$your$organization$isn’t$willing$or$able$to$

standardize$its$use$patterns,$it$will$simply$fail$to$adopt$cloud$technology.

For$the$many$organizations$that$have$already$embarked$on$a$standardization$effort$or$for$those$that$are$

willing$to$start$one,$what’s$next?

RECOMMENDATION 2:

ORGANIZE CLOUD PROJECTS AROUND INFRASTRUCTURE STANDARDIZATION EFFORTS

Too$often,$cloud$adoption$is$presented$as$a$one<dimensional$equation:$

As$we’ve$argued$in$detail,$cloud$has$two$equally$important$essentials.$Infrastructure<only$cloud$efforts$

simply$don’t$move$the$needle.

Infrastructure$and$application$platform$standardization$efforts$are$so$important,$and$use$such$different$

groups$of$people$in$IT,$that$there$is$no$reason$not$to$work$on$them$at$the$same$time.$We$recommend$two$

top<level,$parallel$efforts$in$major$enterprise$cloud$adoption:$One$to$move$toward$elastic,$agile$infrastruc<

ture,$and$one$to$move$toward$standardized,$on<demand$platforms$for$rapid$app$delivery.

RECOMMENDATION 3: DON’T LET THE DETAILS OF CLOUD SWAMP THE HIGHELEVEL INITIATIVES

But$what$about$chargeback$or$showback?$When$should$IT$focus$on$global$cloud$compliance?$What$about$

resource$optimization$and$global$software$catalogs?

These$are$all$important$aspects$of$cloud$(and$many$vendors$stand$ready$to$help$you).$But$chargeback$is$a$

apps$on$standard$platforms,$not$an$end$in$and$of$itself.

We$recommend$focusing$your$effort$on$moving$your$organization$at$least$one$step$up$and$to$the$right$on$

the$cloud$maturity$framework.$Your$architects’$plans$for$making$those$changes$will$drive$detailed$require<

ments$that$call$for$these$detailed$cloud$features$at$the$right$time.

CONCLUSION

So$that’s$the$Enterprise$Cloud$Adoption$Framework.$Our$goal$was$to$cut$through$the$muck$and$mire$to$

provide$a$clear$picture$of$the$graduated$evolution$of$your$cloud$transformation$by$providing$a$set$of$recom<

mendations$that$help$you$advance$your$project$and$create$the$foundation$for$ongoing$success.

We$will$continue$to$use$this$framework$as$the$basis$for$our$practices$and$as$the$kindling$for$critical$public$

debate$on$the$right$way$to$guide$cloud$transformations.$

Have$we$helped?$We$hope$so.$But$we$also$recognize$that$this$is$an$evolution—your$transformation$and$

the$best$practices$that$enable$it.$Let$us$know.$We’re$eager$to$hear$from$you.$

OUR COORDINATES:

Web: www.cloudadoption.org E=mail:$info@cloudadoption.org$ Twitter:$#ECAF

SPONSORED BY:

CONCLUSION So$that’s$the$Enterprise$Cloud$Adoption$Framework.$Our$goal$was$to$cut$through$the$muck$and$mire$to$ provide$a$clear$picture$of$the$graduated$evolution$of$your$cloud$transformation$by$providing$a$set$of$recom< mendations$that$help$you$advance$your$project$and$create$the$foundation$for$ongoing$success. We$will$continue$to$use$this$framework$as$the$basis$for$our$practices$and$as$the$kindling$for$critical$public$ debate$on$the$right$way$to$guide$cloud$transformations.$ Have$we$helped?$We$hope$so.$But$we$also$recognize$that$this$is$an$evolution—your$transformation$and$ the$best$practices$that$enable$it.$Let$us$know.$We’re$eager$to$hear$from$you.$ OUR COORDINATES: Web: www.cloudadoption.org E=mail: $info@cloudadoption.org$ Twitter: $#ECAF
CONCLUSION So$that’s$the$Enterprise$Cloud$Adoption$Framework.$Our$goal$was$to$cut$through$the$muck$and$mire$to$ provide$a$clear$picture$of$the$graduated$evolution$of$your$cloud$transformation$by$providing$a$set$of$recom< mendations$that$help$you$advance$your$project$and$create$the$foundation$for$ongoing$success. We$will$continue$to$use$this$framework$as$the$basis$for$our$practices$and$as$the$kindling$for$critical$public$ debate$on$the$right$way$to$guide$cloud$transformations.$ Have$we$helped?$We$hope$so.$But$we$also$recognize$that$this$is$an$evolution—your$transformation$and$ the$best$practices$that$enable$it.$Let$us$know.$We’re$eager$to$hear$from$you.$ OUR COORDINATES: Web: www.cloudadoption.org E=mail: $info@cloudadoption.org$ Twitter: $#ECAF