strategies for devops in the api and microservices world
TRANSCRIPT
World®’16
StrategiesforDevOpsintheAPIandMicroservicesWorldJayThorne- ConsultingSoftwareEngineer,APIM- CATechnologies
DO3X82V
DEVOPS
2 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD
©2016CA.Allrightsreserved.Alltrademarksreferencedhereinbelongtotheirrespectivecompanies.
Thecontentprovidedinthis CAWorld2016presentationisintendedforinformationalpurposesonlyanddoesnotformanytypeofwarranty. The informationprovidedbyaCApartnerand/orCAcustomerhasnotbeenreviewedforaccuracybyCA.
ForInformationalPurposesOnlyTermsofthisPresentation
3 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD
Abstract
Ascompaniesinvestindeveloper-operations-styledeployment(DevOps),theinterfacesandtoolingnecessarytobesuccessfulinDevOpsbegforsimplificationasamajorfocusofprojects.LearnhowtheCAAPIManagementunitisapproachingDevOpsenablementandprovidingasafeandscalablewaytoutilizeAPIsandmicroservices tohelpcustomersrealizeROIontheirDevOpsinvestments.Inthissession,we’llexplorehowtoenableDevOpsintheworldofmicroservicesusingAPImanagementtooling,anddiscusshowmanyofourcustomers’traditional,operations-focusedinstallationsareevolvingorcouldbeevolvedintoDevOps-focuseddeployments.Properlyexecuted,theworldofmicroservices practicallydefinessimplicity;APImanagementandDevOpsareacrucialpartofthatpathtosuccess.
JayThorneCATechnologiesConsultingSoftwareEngineer
4 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD
Agenda
REALITIESOFMICROSERVICES
STRATEGIES
CONCLUSION
1
2
3
5 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD
TheRealities
§ Corporatestraitjacket– GovernanceiscalledChangeControlandmostlymeans
ChangePrevention– “That’sthewaywe’vealwaysdoneit”:
§ Can’tinnovatesotimetomarketislong
TheBigOps/BigDevExtreme
CHANGES
6 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD
TheRealities
§ Lunaticsrunningtheasylum– It’smicroservices allthewaydown– 8versionsofsamecapability– Devs writeeverything,sowedon’tneedops– Wedidn’tknowbutitwenttoproduction
TheLeanandMeanExtreme
CONTROLS
7 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD
Strategy:SmallerInitialProject
§ Learningtheropesofmicroservices /DevOpsoncorebusinessisabadidea
§ Microservices designisdifferent– Intentionallyreducedscope– Loweringdependenciesisdifficultatfirst
LearnHowThisStuffWorksFirst
BETYOUR
BUSINESS
NEWPROJECT
8 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD
Strategy:FocusonSizeofDeliverables
§ Bigdependencies=strictersequences=longerinstall/upgradewindows
§ Largerartifacts=longerbuilds/installs/startup
§ Manualinstall=moreopportunitiesforfatfingering
ReduceDependencies
HUGE
9 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD
Strategy:FocusonSmallerDeliverables
§ Lowerdependences=opportunitiesforasynchronousdeployment
§ Smallerartifacts=quickdeploy,quickrevert
§ Automation=nomissedsteps,smallerrunbooks
ReduceDependencies
SMALLISBEAUTIFUL
10 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD
NUKEandPAVE
Strategy:Don’tUpgrade- Replace
§ Buildfor“configurefromscratch”wherepossible– Upgradebecomes“Runnewcodewith
previousconfiguration”– Rollbackbecomestrivial
§ Microservices canseparatedatastorefrombusinesslogic– usethisifyoucan
UpgradesAreaLotofWork
11 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD
Strategy:Don’tMakeReuseaStrictDesignGoal
§ Similar(butnotequal)mightrequireseparatetool
§ FocusonnotduplicatingIdenticaltools
§ Don’tnitpickonsimilarity
§ However:Subsets/supersetsdon’timplyseparatetools
ReuseIsAnotherWayofSayingDependency
12 ©2016CA.ALLRIGHTSRESERVED.@CAWORLD#CAWORLD
Conclusion:Learn toBuild,DeploySmall
§ Biasforsizeanddependencyreduction
§ Learnhowtoworkbiasforsizeinyourorganization
§ Dependenciesneedexplicitattention
§ Applylearning
HaveYourCakeandEatItToo
SlowFastLargeSmallSafeShortTimeToMarket