• Partner of the company
• Keep the technology side of our projects excellent
Slide 9
Slide 9 text
Our path to
continuous delivery
Slide 10
Slide 10 text
No content
Slide 11
Slide 11 text
From Nebula
to Heroku
Slide 12
Slide 12 text
No content
Slide 13
Slide 13 text
Continuous
integration server
Slide 14
Slide 14 text
No content
Slide 15
Slide 15 text
Alerting
Slide 16
Slide 16 text
Monitoring
Slide 17
Slide 17 text
No content
Slide 18
Slide 18 text
No content
Slide 19
Slide 19 text
• Automation
• Everything under version control
• Hosted platforms
• Open-source
• Cross-service integration
• Visibility
Slide 20
Slide 20 text
Pain
Slide 21
Slide 21 text
• Don't brush it off
• Listen to your pain
• Let it guide you
Slide 22
Slide 22 text
"... broke again!"
Slide 23
Slide 23 text
"Why do we
always ...?"
Slide 24
Slide 24 text
"I waste time on this
on every project"
Slide 25
Slide 25 text
• A er you've become conscious of the pain
you can try to remove the source of it
• Learning new techniques, languages and tools
makes you discover new pains
• Life will never be pain free so why not use it
as a valuable tool
Slide 26
Slide 26 text
• Heroku was relief to the pain of not having automated server
administration
• Monitoring was relief to the pain of not having visibility
• Moving alerting from email to a centralized system was also relief to
the lack of visibility
• Continuous integration server was the relief for not having certainty
Slide 27
Slide 27 text
Future
Slide 28
Slide 28 text
"The future is
already here
—
it's just not very evenly
distributed."
Slide 29
Slide 29 text
• Need for faster feedback, confidence and predictability is always there
• Tools are ge ing be er everywhere
• For us: automatic deployment to staging
Slide 30
Slide 30 text
• Currently proprietary platforms are ahead
• Self-hosted and open-source solutions will get there
• I see this as the way most services should be built and run in the future
Slide 31
Slide 31 text
• Cultures will change
• From Hollywood launches to more incremental and iterative approach
• Feature flags, stealth launches, deploying the backend first…
Slide 32
Slide 32 text
TODO
Slide 33
Slide 33 text
• What is the most painful part of your system and how could your team
minimize that pain?
• Did I talk about a technology or process unknown to you? Take 15
minutes tomorrow and investigate it.
• Is there a blocker for implementing one of the continuous integration
practices? Can that be solved?