holistic devployment Piotr Żołnierek @pzol why the last mile is the longest
Agile EE2011 holistic devployment
May 28, 2015
Your agile team has built great software, only to find out it cannot work in production?
Agile has taken the development community by storm. It has improved our everyday lives. It enables us to build great working software in all kinds of environments. But for many companies, covering the last mile, bringing an application into production is the biggest obstacle to being truly agile. Prescribed processes and skill-sets in operations lag behind a decade. We have created cross-functional teams, excluding one of the most important aspects of software – it needs to run in production!
Agile has taken the development community by storm. It has improved our everyday lives. It enables us to build great working software in all kinds of environments. But for many companies, covering the last mile, bringing an application into production is the biggest obstacle to being truly agile. Prescribed processes and skill-sets in operations lag behind a decade. We have created cross-functional teams, excluding one of the most important aspects of software – it needs to run in production!
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
holistic devployment
Piotr Żołnierek
@pzol
why the last mile is the longest
anixe
anixe
cowboy deployment process
anixe
anti-patterns
ad-hoc releases
production patching
service monolith
lack of automation
anixe
the sheriff is in town
anixe
separation of concerns
SoftwareDevelopment
QA
TechnologyOperations
web applicationsversioning
software architectureshared applications
research & development
deploymentinfrastructure
QAtechnical analysis
24x7 supportsystems & app administration
anixe
conflict of interests
SoftwareDevelopment
TechnologyOperations
change preservation
release is riskavailabilitystability
reliability
new featuresrelease often
anixe
anixe
anti-patterns
ad-hoc releases
production patching
service monolith
lack of automation
over the wall deployment
anixe
solution 1: upgrade admins to devops
TechnologyOperations
SoftwareDevelopment
devops = sysadmins with coding knowledge
cons- silos- dev not responsible for production
pros+ ops can lookup code + ops can automate platform install/deploy+ ops can better understand app+ ops can write tests
anixe
solution 2: no-opsSoftware
Development&
TechnologyOperations
one really cross-functional team
cons- 24x7 support- dev must know hardware/infrastructure- dev must know all customer configs
pros+ all understand app+ common responsibility
anixe
solution 3: cloud
SoftwareDevelopment
TechnologyOperations
deploymentapp administration
web applicationsversioning
software architectureshared applications
research & development
infrastructuretechnical analysis
24x7 supportsystems administration
cons- silos- support difficult, lack of knowledge of app
pros+ internal/outsource infrastructure doesn’t matter+ devs responsible for production done
anixe
how far have we come?
devs build, test and write deploy scripts
ops run deploy scripts
dbs do db migrations via script
windows
devs build, test and deploy
devs deploy via scripts
scripts do db migrations
linux
devs write app management scripts
our current solution: cloud
anixe
good devployment patterns
automation
self-check
code-data split
composite deployment
adaptive deployment
anixe
thanks!
Piotr Żołnierek
speakerrate.com/pzol
@pzol
http://speakerrate.com/talks/8378-holistic-deployment
Related Documents
