Taming a beast - Bol.com's journey from deploying once a month to more then once a day - Mike Chernev - Codemotion Amsterdam 2018

> whoami> whoami
Addicted to technology
Reads manga
Star Wars fan
Struggles to play the guitar
@MikeChernev@MikeChernev
@MikeChernevCodemotion Amsterdam 2018: Taming a beast

AgendaAgenda
1. Perspective1. Perspective
2. define: beast2. define: beast
4. Taming the beast4. Taming the beast
3. Why not3. Why not slayslay it it
5. Lessons learnt5. Lessons learnt

> whois bol.com> whois bol.com

bol.com ~ 18 years agobol.com ~ 18 years ago
One applicationOne application
One DeploymentOne Deployment

4 weeks
Time
Release cycleRelease cycle

4 weeks
Time

Stuck in the past
Stuck in the past

Time
2 weeks 2 weeks

define: beastdefine: beast
Large monolithLarge monolith
++
Legacy systemLegacy system
UnmanageableUnmanageable
++
==
BeastBeast

define: beastdefine: beast
> 900 commits> 900 commits
> 70 engineers> 70 engineers

Slow release cycle = Slow progressSlow release cycle = Slow progress

How to tame a beast?How to tame a beast?
Through being able to change it at a fast andThrough being able to change it at a fast and
stable pacestable pace

Continuous DeliveryContinuous Delivery

Continuous Delivery (CD)Continuous Delivery (CD)
“Continuous Delivery is a software development“Continuous Delivery is a software development
discipline where you build software in such a waydiscipline where you build software in such a way
that the software can be released to production atthat the software can be released to production at
any time.”any time.”[1][1]
Martin Fowler

Problems with CDProblems with CD

"Problems, causes and solutions when adopting"Problems, causes and solutions when adopting
continuous delivery—A systematic literature review."continuous delivery—A systematic literature review."
Laukkanen, Eero, Juha Itkonen, and Casper Lassenius.Laukkanen, Eero, Juha Itkonen, and Casper Lassenius.
Information and Software Technology 82 (2017): 55-79.Information and Software Technology 82 (2017): 55-79. [2][2]

"Problems, causes and solutions when adopting"Problems, causes and solutions when adopting
continuous delivery—A systematic literature review."continuous delivery—A systematic literature review."
Laukkanen, Eero, Juha Itkonen, and Casper Lassenius.Laukkanen, Eero, Juha Itkonen, and Casper Lassenius.
Information and Software Technology 82 (2017): 55-79.Information and Software Technology 82 (2017): 55-79. [2][2]
published February 2017
(2 months after we started)

Build design Complex build, inflexible build
System design System modularization, unsuitable architecture, internal dependencies, database
schema changes
Integration Large commits, merge conflicts, broken build, work blockage, long-running
branches, broken development flow, slow integration approval
Testing Ambiguous test result, flaky tests, time-consuming testing, hardware testing, multi-
platform testing, UI testing, untestable code, problematic deployment, complex
testing
Release Customer data preservation, documentation, feature discovery, marketing, more
deployed bugs, third party integration, users do not like updates, deployment downtime
Human and
organizational
Lack of discipline, lack of motivation, lack of experience, more pressure, changing
roles, team coordination, organizational structure
Resource Effort, insufficient hardware resources, network latencies

Integration merge conflicts, work blockage, long-running
branches,
Testing flaky tests, time-consuming testing,
problematic deployment,

Release feature discovery,

Human and
organizational
Lack of discipline, lack of motivation, lack of experience,
team coordination,
Build design Complex build, inflexible build
System design System modularization, unsuitable architecture, internal dependencies, database
schema changes
Integration Large commits, broken build,
broken development flow, slow integration approval
Testing Ambiguous test result, hardware testing, multi-
platform testing, UI testing, untestable code, complex
testing
Release Customer data preservation, documentation, marketing, more
deployed bugs, third party integration, users do not like updates, deployment downtime
Human and
organizational
more pressure, changing
roles, organizational structure
Resource Effort, insufficient hardware resources, network latencies
Problems with CDProblems with CD (for our application)(for our application)

Flaky Tests, Time-consuming testingFlaky Tests, Time-consuming testing
ProblemProblem

SolutionSolution

ResultResult

Lack of discipline, lack of motivation, lack of experienceLack of discipline, lack of motivation, lack of experience
ProblemProblem

SolutionSolution

ResultResult

Long running branches, merge conflicts, work blockageLong running branches, merge conflicts, work blockage
ProblemProblem

SolutionSolution

ResultResult

Feature discovery, team coordination, problematic deploymentsFeature discovery, team coordination, problematic deployments
ProblemProblem

SolutionSolution

ResultResult

ResultsResults
30 releases instead of 430 releases instead of 4
446 features realeased446 features realeased
TTL 4 days vs 1.5 weeksTTL 4 days vs 1.5 weeks

AgendaAgenda
1. Perspective1. Perspective
2. define: beast2. define: beast
4. Taming the beast4. Taming the beast
3. Why not3. Why not slayslay it it
4a. A look into the future4a. A look into the future
5. Lessons learnt5. Lessons learnt

What's next?What's next?
“The past is always tense,“The past is always tense,
the future perfect.”the future perfect.”
Zadie Smith Zadie Smith

What's next?What's next?
[3] [4] [5]
"Rapid release "Rapid release
at massive scale"at massive scale"[3][3]
[4]

Feature togglesFeature toggles
““Feature Toggles Feature Toggles
(aka Feature Flags)(aka Feature Flags)””[6][6]
Martin Fowler

Stable and reliable tests suiteStable and reliable tests suite
Proper branching strategyProper branching strategy
Lessons learntLessons learnt
Visibility on your pipelineVisibility on your pipeline
Effective communicationEffective communication
Stable and reliable tests suiteStable and reliable tests suite

TeamTeam

Thank you!Thank you!
Questions?Questions?

ReferencesReferences
[1] https://martinfowler.com/bliki/ContinuousDelivery.html
[2] https://doi.org/10.1016/j.infsof.2016.10.001
[3] https://code.facebook.com/posts/270314900139291/rapid-
release-at-massive-scale
[4] https://blog.launchdarkly.com/toggle-talk-with-josh-wills
[5] https://blogs.dropbox.com/tech/2017/03/introducing-
stormcrow
[6] https://martinfowler.com/articles/feature-toggles.html

Taming a beast - Bol.com's journey from deploying once a month to more then once a day - Mike Chernev - Codemotion Amsterdam 2018

Recomendados

Recomendados

Más contenido relacionado

Similar a Taming a beast - Bol.com's journey from deploying once a month to more then once a day - Mike Chernev - Codemotion Amsterdam 2018

Similar a Taming a beast - Bol.com's journey from deploying once a month to more then once a day - Mike Chernev - Codemotion Amsterdam 2018 (20)

Más de Codemotion

Más de Codemotion (20)

Último

Último (20)

Taming a beast - Bol.com's journey from deploying once a month to more then once a day - Mike Chernev - Codemotion Amsterdam 2018