Devops in Practice Reliable and automated software delivery

260 Pages·2014·18.113 MB·English

by  Danilo Sato

© CodeCrushing
AllrightsreservedandprotectedbytheLawnº9.610,from10/02/1998.
No part of this book can be neither reproduced nor transferred with-
out previous written consent by the editor, by any mean: photographic,
eletronic,mechanic,recordingoranyother.
CodeCrushing
Booksandprogramming
RuaVergueiro,3185-8ºandar
04101-300–VilaMariana–SãoPaulo–SP–Brasil
CodeCrushing
Dedication
“Tomydad,whointroducedmetotheworldofcomputersandismylife-long
rolemodel."
i

CodeCrushing
Preface
JezHumble
Shortlya￿erIgraduatedfromuniversityin￿￿￿￿, Igotajobatastart-upin
London.Myboss,JonnyLeRoy,taughtmethepracticeofcontinuousdeploy-
ment:Whenwewere￿nishedwithanewfeature,wewoulddoaquickmanual
smoketestonourworkstationandthen￿ptherelevantASPscriptsdirectly
ontotheproductionserver–notapracticeIwouldrecommendtoday,butit
didhavetheadvantageofenablingustogetnewideastoourusersquickly.
In￿￿￿￿Ijoined￿oughtWorkswheremyjobwastohelpenterprisesde-
liverso￿ware,andIwasappalledtodiscoverthatleadtimesofmonthsoreven
yearswerecommon.Fortunately,Iwasluckyenoughtoworkwithanumber
of smart people in our industry who were exploring how to improve these
outcomeswhilealsoincreasingqualityandimprovingourabilitytoserveour
users. ￿e practices we came up with also made life better for the people
we were working with (for example, no more deployments outside of busi-
ness hours) – an important indication that we were doing something right.
In ￿￿￿￿, Dave Farley and I published “ Continuous Delivery,” in which we
describe the principles and practices that make it possible to deliver small,
incrementalchangesquickly,cheaply,andatlowrisk.
However, our book omits the nuts and bolts of how one actually gets
started creating a deployment pipeline, put in place monitoring and infras-
tructure as code, and the other important, practical steps needed to imple-
ment continuous delivery. ￿us I am delighted that Danilo has written the
bookthatyouhaveinfrontofyou, whichIthinkisanimportantandvalu-
ablecontributiontothe￿eld.Danilohasbeendeeplyinvolvedinhelpingor-
ganizationsimplementthepracticesofcontinuousdeliveryforseveralyears
andhasdeepexperience,andIamsureyouwill￿ndhisbookpracticaland
iii
CodeCrushing
informative.
Iwishyouallthebestwithyourjourney.
iv
CodeCrushing
About the book
Deliveringso￿wareinproductionisaprocessthathasbecomeincreasingly
di￿cult in IT department of various companies. Long testing cycles and a
divisionbetweendevelopmentandoperationsteamsaresomeofthefactors
that contribute to this problem. Even Agile teams that produce releasable
so￿ware at the end of each iteration are unable to get to production when
theyencounterthesebarriers.
DevOps is a cultural and professional movement that is trying to break
down those barriers. Focusing on automation, collaboration, tools and
knowledgesharing,DevOpsisshowingthatdevelopersandsystemengineers
havemuchtolearnfromeachother.
Inthisbook,weshowhowtoimplementDevOpsandContinuousDeliv-
ery practices to increase the deployment frequency in your company, while
alsoincreasingtheproductionsystem’sstabilityandreliability.Youwilllearn
howtoautomatethebuildanddeploymentprocessforawebapplication,how
toautomateinfrastructurecon￿guration,howtomonitortheproductionsys-
tem,aswellashowtoevolvethearchitectureandmigrateittothecloud,in
additiontolearningseveraltoolsthatyoucanapplyatwork.
v

CodeCrushing
Acknowledgements
To my father, Marcos, for always being an example to follow and for going
beyondbytryingtofollowthecodeexampleswithoutanyknowledgeofthe
subject.Tomymother,Solange,andmysister,Carolina,forencouragingme
andcorrectingseveraltyposandgrammarmistakesonpreliminaryversions
ofthebook.
Tomypartnerandbestfriend,Jenny,forhercareandsupportduringthe
manyhoursIspentworkingonthebook.
Tomyeditor,PauloSilveira,forgivingmethechance,andknowinghow
toencouragemeattherighttimeinorderforthebooktobecomeareality.
To my reviewer and friend, Vivian Matsui, for correcting all my grammar
mistakes.
Tomytechnicalreviewers: HugoCorbucci,DanielCordeiroandCarlos
Vilella. ￿anksforhelpingme￿ndbetterwaystoexplaindi￿cultconcepts,
forreviewingterminology,forquestioningmytechnicaldecisionsandhelp-
ingmeimprovetheoverallcontentsofthebook.
TomycolleaguesPrasannaPendse,EmilyRosengren,EldonAlmeidaand
othermembersofthe“Blogger’sBloc”groupat￿oughtWorks,forencourag-
ingmetowritemore,aswellasasforprovidingfeedbackontheearlychapters.
To my many other colleagues at ￿oughtWorks, especially Rolf Russell,
Brandon Byars and Jez Humble, who heard my thoughts on the book and
helpedmechoosethebestwaytoapproacheachsubject,chapterbychapter.
Finally,toeveryonewhocontributeddirectlyorindirectlyinwritingthis
book.
￿ankyousomuch!
vii