 does the operations tool chest change? How does the required skill set differ? How are the interactions between operations and other IT and business organizations different from in the past? How can operations provide the confidence to the entire organization that this new pipeline is still delivering non-functional requirements such as regulatory compliance and a secure and certified operating environment? How does operations safely consume vendor and upstream dependencies while meeting developer desires for the latest and greatest?

Operations is more important than ever for a business to derive value from its IT organization. But the roles and the goals of operations are significantly different than they were historically.

Tuesday, November 01, 2016

if you're ignoring PaaS because early offerings didn’t meet your needs or because you’re more focused on operations than developers, you should look again. It enables ops to enable developers efficiently and to manage an underlying container infrastructure.

Circulating in drafts beginning in 2009, some variant of the NIST Cloud Computing definition used to be de rigueur in just about every cloud computing presentation. Among other terms, this document defined Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS), and Software

-as-a-Service (SaaS) and, even as technology has morphed and advanced, this is the taxonomy that we still largely accept and adhere to today.

That said, PaaS was never as crisply defined as IaaS and SaaS because “platform” was never as crisply defined as infrastructure or (end-user) software. For example, some platforms were specific to a SaaS, such as Salesforce.

Others, specifically the online platforms that were most associated with the PaaS term early on, were typically tied to particular languages and frameworks. These PaaSs were very “opinionated.” For example, the original Google App Engine supported an environment that was just (and just almost) Python and Heroku was all about Ruby. Heroku's twelve-factor app manifesto was an additional type of opinion; write your apps this way or they won’t really be suitable for the platform. These platforms may not have been just for hobbyists, but they were certainly much more suited to developer prototyping and experimentation than production deployments.

At the same time, platform was also used more broadly to cover the integration of a range of middleware, languages, frameworks, other tools, and architecture decisions (
does the operations tool chest variety? How does the command skill set differ? How are the interaction between operation and other IT and commercial enterprise organizations different from in the past? How can process provide the confidence to the integral organization that this new pipeline is still deliver non - functional requirements such as regulatory compliance and a secure and certifiable operating environment? How does operations safely consume vendor and upstream addiction while meeting developer desires for the late and greatest? 

 operation is more important than ever for a business to derive value from its IT organization. But the function and the goals of operations are significantly different than they were historically. 

 Tuesday, November 01, 2016 

 if you're ignoring PaaS because early offerings did n’t meet your needs or because you ’re more focused on operations than developers, you should look again. It enables ops to enable developers efficiently and to manage an underlying container infrastructure. 

 Circulating in drafts begin in 2009, some variant of the NIST Cloud Computing definition used to be de rigueur in barely about every cloud computing presentation. Among other term, this document defined Infrastructure - as - a - Service (IaaS), Platform - as - a - Service (PaaS), and Software 

 -as - a - Service (SaaS) and, even as technology has morph and advanced, this is the taxonomy that we still largely accept and adhere to today. 

 That said, PaaS was never as sharply defined as IaaS and SaaS because “ platform ” was never as crisply defined as infrastructure or (end - user) software. For model, some platforms were specific to a SaaS, such as Salesforce. 

 Others, specifically the online platforms that were most associated with the PaaS condition early on, were typically tied to especial languages and frameworks. These PaaSs were very “ opinionated. ” For example, the original Google App Engine supported an environment that was precisely (and just almost) Python and Heroku was wholly about Ruby. Heroku's twelve - factor app manifesto was an additional type of opinion; publish your apps this way or they wo n’t very be suitable for the platform. These platforms may not have been just for hobbyists, but they were surely much more suited to developer prototyping and experimentation than output deployments. 

 At the same time, platform was also use more broadly to cover the integration of a stove of middleware, languages, frameworks, early tools, and architecture decisions (
 dofs the operations tool cmest change? How bies thx requided skilu set differ? How are the intxracrions between operations ana other IN and busunesw organizatmkns difnzrent nrom nn the past? How gan operatimns provide tha zoufidence to the entire organization ehat thos new pipeline ys suilj dempvtring non-functional requirements auch as regulatory cpmpliance and a secure and cerhified operating ejvironment? Yow qies operatiovs safely bmnsume vensor and upstream dependencies wfile keeting deceoopft desires foc the jatest and gvvatest?

O[eratioms is more impprtent rhan ever for a businxss to derive value srom its HT organization. But tye rones dnd gye eoams or operwtikns are sifnificantly different than theu rvte historicamly.

Tuefdwy, November 01, 2016

if you're ignoring PaaS becduss early offerings didn’t meet your needs or bgcause you’we more focused on operations than developers, you shouma lioh qgwin. It enables ops to enable developers efficysnuly and to manage an underlyonh vjntainer infrxstrucchrs.

Circulating in drwfts bedinnibg in 2009, soie vsriant of the NIST Cloud Conputing defiuituon used to be de xigueur in jbst abput efery cloud computing przsentafion. Among lther terjr, this document aefpned Infrastructure-as-a-Service (YaaS), Plathorm-ax-a-Servize (PsaS), anq Software

-ws-a-Seveice (SaaS) and, even as tgchnolmgy has mogphed and advanced, this is the vexonomy that ee stpll largejy acgept and adhere to today.

That xaid, PacS was never as brisply dxfined as IawS and SaaS bafause “platfocm” was neder qs ceisply adfined as infrsstructurv jr (ebd-user) software. Fov exaolle, some platfoxow were specific to a FawS, stwh as Salesfmrce.

Uthdts, spdcifically bhe onlone platforms that ware jost associated wiyh the PaaW term ewrly on, were yypically tied to karticnlar lenguagrs wnd frameworks. These PaaSs wers very “oplnijnated.” For evampoe, the origiual Google App Engine supported an envirinment that was jost (and just almost) Pithpn and Herolu waf all abogt Ruby. Heroku's twelce-factor app maninesto was an additionam type of ooinion; write your apps this way or they won’t really be suitable for the poatform. These platrormx may njc have feen oust for hobbyistx, but they were certainly much oore suideb to developer prototyping anc dxperimentatiun than production deplogments.

At the same time, platform was alsp used more broadly to cpver the intefration of a range of middleeare, lcnguagws, framwworns, other toolr, amd architechure dzcisions (
does the operations tool chest change? How required set differ? are the interactions and organizations different from the past? How operations provide the confidence to the organization that this new pipeline is still delivering non-functional requirements such as regulatory and a secure and certified operating environment? How does operations safely consume vendor upstream while developer for the latest and greatest? Operations is more important than ever for a business to derive from its IT organization. But the roles and goals of operations are different than they were historically. November 2016 if ignoring because offerings didn’t meet needs or because you’re more focused on operations than developers, you should look again. It enables ops enable developers to manage underlying infrastructure. in drafts beginning some variant of the NIST Cloud to be de rigueur in just about every computing presentation. other terms, this document defined Infrastructure-as-a-Service Platform-as-a-Service (PaaS), and Software -as-a-Service (SaaS) and, even technology has morphed and advanced, this is the taxonomy that we still largely accept and today. That said, PaaS never as crisply as and because was never crisply defined as infrastructure or (end-user) software. For example, some platforms specific to a SaaS, such as Salesforce. Others, specifically the that most associated with PaaS term early on, typically to particular languages and PaaSs very the Google Engine supported an environment was just (and just almost) and Heroku was all manifesto was an additional type of opinion; write apps this way or they won’t really suitable for the platform. These platforms may not have been just for but they much more suited to developer prototyping and experimentation production deployments. At the time, platform was also used more broadly to cover integration a range middleware, languages, frameworks, tools, and architecture (
 does the operations tool chesT change? How Does tHe rEquIrEd skIll sEt differ? How are THe inTeractions between operaTions AnD OtheR iT And buSiness oRGaNIZatIoNs DifFeREnT from In tHe past? HOw can operaTioNs Provide the coNFiDence to the EntIre organizatIon That thIs New PIpeliNe iS stilL delivERing noN-functionAl REquireMEnts sucH AS rEgulAtory compliance anD A sECure and certifiEd operAtINg ENVirOnmEnt? How does OpEratiONs safelY CoNSUMe vENdor and upstreAm dependencIEs wHile meEtIng DEvelopEr desIrES foR the latest aNd grEatest?

OpeRationS Is more iMPortant Than evEr fOr a BusiNEsS tO deRiVE vaLUe FroM Its iT organiZaTiOn. But The rOLES And tHe gOals Of opeRations are sigNifIcanTLy dIfferEnt thAn thEy Were hIstoriCally.

tuEsday, November 01, 2016

if You'rE ignoring paas bEcaUsE earlY OfferiNgs DidN’t meet yOur needS Or bEcAUSE yOu’re more focused on oPeRATiOns than dEvelopERs, YoU Should loOk AgaIn. It ENAbles Ops tO EnAble deveLopers EFfIcIently aNd To manaGe An uNdeRlyinG ContAiner iNfrastruCture.

cIrculating in drAFts beginning iN 2009, SoME VaRIant Of tHe NIST Cloud compUTing DefiNItIon USed to Be de rIgUEuR In just about every cloUd ComputIng prEsentation. AmoNg other terMS, THis documEnt dEFiNEd InfrastructuRe-as-a-service (Iaas), platform-As-a-SeRvice (Paas), and SoftwARE

-as-a-ServIce (saas) anD, evEN As Technology has MORpheD aNd advanCed, This is tHe tAxoNomY thAt We still laRgely accEpT aNd AdHerE to toDAy.

That saId, paas wAs nEver aS CrisplY defiNed aS IAas And saaS becAUsE “PLatfOrM” wAs neVer As CrispLy deFIneD as infrAstructurE or (ENd-usEr) SoFtware. FOr example, some PlAtforms werE sPecIfic to A sAaS, such aS Salesforce.

Others, specifICally thE onLine pLatfOrms that wEre Most asSocIAted wiTh the PAaS teRm EarLY On, werE TYpIcaLlY tied to parTICulAr lanGuAges And framEworks. These PaaSs weRE veRy “opinionated.” for ExamPLE, tHe oRIgINal goOGle aPP Engine supporteD an environMeNT tHat was just (ANd jUsT almost) python aNd HerOKu was alL about RubY. Heroku's tWeLve-fACTor App manifesTo was an aDditional TYpe of OPiNion; wRitE your aPpS thIs way Or they WOn’t ReallY be suiTaBle for The plAtForm. ThesE platforms may not have beeN just fOr hobByiSts, but theY weRE ceRtainly muCh moRe suited to DevEloPer prOtoTYping And eXPeRimENtatiOn thAN productiON dEplOYMeNts.

At the samE TIMe, pLatfoRm wAS also uSed mOre broadly to cover THe integration oF a raNGE of MidDLewaRe, Languages, frameWorKs, OTHer tools, AnD architectuRe decisiOnS (
 does the operations toolchest chan ge? H owdoe stherequ ired skill set diff er? How are the intera ction sb etwe e nopera tions a n do t her  I Tand  b u si nessorg anizati ons differ ent  f rom in the p a st ? How canope rations prov ide  the c on fid e nce t o t he en tire o r ganiza tion that  t h is new pipelin e is  sti ll delivering non - fu n ctional requir ements  s u ch a s r egu latory com pl iance and a s e cu r e and certified ope rating envi r onm ent? H ow  do e s oper ation ss afe ly consumevend or and up stream depende n cies wh ile me eti ngdeve l op er  de si r esf or  th e  la test and  g re atest ?

O p e r a tion s i s mo re im portant thaneve r fo r  abusin ess t o de ri ve va lue fr om it sIT organization . Bu t the rol esan d t he  goal s  of op era tio ns aresignifi c ant ly d i ff erent than they we re h is toricall y.

Tu e sd ay ,  Novembe r01,  201 6 
if y ou'r e  i gnoringPaaS b e ca us e early  o fferin gs  di dn’ t mee t  you r need s or bec ausey ou’re more foc u sed on operat i on s th a n de vel opers, youshou l d lo ok a g ai n.I t ena blesop s  t o  enable developersef ficien tly a nd to managean underly i n g  contain er i n fr a structure.

Ci rcula ting in dr a fts begi nning  in 2009 , some va r i ant of t heNIS T C lou d Co mputing defin i t ionus ed to b e d e rigue urinjus t a bo ut everycloud co mp ut in gpre senta t ion. Amo ng  ot he r t erms, this d ocume nt d ef in e d I nfrastr u ct u r e-as -a -S ervi ce(I aaS),  Pla t for m-as-a- Service ( Paa S ), a nd  S oftware 

-as-a-Servi ce  (SaaS) an d,  ev en ast e chnology  has morphed and advanc e d, this  is  thetaxo nomy that  we  still  la r gely a cceptand a dh ere t o tod a y .
Th at  said, Paa S was  neve ras c risplydefined as IaaS an d  Sa aS because “p lat form ” wa s n e ve r  as  c r isp l y  defined as inf rastructur eo r(end-user) sof tw are. Fo r examp le, s o me plat forms wer e specifi cto a S aaS , such asSalesfor ce.

Othe r s, sp e ci fical lythe on li neplatf orms t h atweremost a ss ociate d wit hthe PaaS  term early on, were ty picall y tie d t o particu lar lan guages an d fr ameworks.The sePaaSs  we r e ver y “o p in ion a ted.”  For example,t he  or i g in al Google A p p Eng ine s upp o rted a n en vironment that wa s  just (and jus t al m o st)  Py t honan d Heroku was a llab o u t Ruby.He roku's twel ve-facto ra pp ma nifest o wasan addi t i on a l type  ofopi nion; wri teyo u r appsth is way or  the ywon’treally be s u i table for the pl atfor m .  Thes e  pl atfor ms  may no t  hav e been jus t for hobby ists,buttheywere ce rt ainlymuc hmore suite d  to devel operprototy pi ng a ndexperi ment a t ion t hanpr odu ction dep l o ym e nt s. 
At  the  same  t ime,  platform was also  us e d morebr oad l y  to co v er t he integra tio n ofa range of m i ddle w ar e , lan guages , fram eworks, oth er  tools,  an d architect ure decis i ons  ( 
 does_the operations_tool chest change? How_does the_required_skill set_differ?_How are the_interactions between operations_and other IT and_business organizations different_from_in the past? How can operations provide the confidence to the entire organization that_this_new pipeline_is_still_delivering non-functional requirements such as_regulatory compliance and a secure_and certified_operating environment? How does operations safely consume vendor_and_upstream dependencies while_meeting developer desires for the latest and greatest?

Operations is_more important than ever for a_business to derive_value_from_its IT organization. But_the roles and the goals of_operations are significantly different than they_were historically.

Tuesday, November 01, 2016

if you're ignoring_PaaS because early offerings didn’t meet_your needs or because you’re_more focused_on operations than developers, you_should look again._It enables_ops to enable_developers efficiently and to manage an_underlying container infrastructure.

Circulating_in drafts beginning in 2009, some_variant_of the NIST_Cloud_Computing_definition used_to be de_rigueur_in just_about_every cloud computing presentation. Among other_terms,_this document defined Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS),_and Software

-as-a-Service (SaaS) and,_even_as technology has morphed_and advanced, this is the_taxonomy that we still largely accept_and adhere_to today.

That_said, PaaS was never as crisply defined as IaaS and SaaS_because “platform” was never as crisply_defined as infrastructure or_(end-user) software._For_example, some platforms_were_specific to_a SaaS, such as Salesforce.

Others, specifically the_online platforms_that were most associated with the_PaaS term early on,_were_typically tied to particular languages and_frameworks. These PaaSs were very “opinionated.”_For example, the original Google_App_Engine_supported an environment that was_just (and just almost) Python and_Heroku was all_about Ruby. Heroku's twelve-factor app manifesto was_an_additional type of opinion; write your_apps_this way or they won’t really_be_suitable_for the platform. These platforms_may not have been just for_hobbyists, but they were certainly much more suited to_developer prototyping and_experimentation than production deployments.

At the_same_time,_platform was also used more broadly to cover the integration_of a_range of middleware,_languages, frameworks, other tools, and architecture decisions (