bursting the pipeline: evolving continuous delivery at mixradio
DESCRIPTION
The team at MixRadio has been experimenting with DevOps and Continuous Delivery for many years with notable success. They will share with us their insights into Continuous Delivery, particularly how their approach to deployment changed as they created their second generation of tooling for cloud deployment and how the Continuous Delivery 'Pipeline' metaphor became less relevant. A talk given at the London Continuous Delivery Meetup, June 19th 2014.TRANSCRIPT
Bursting the PipelineEvolving Continuous Delivery
at
@joelittlejohn
History
Dr. Strangelove © 1963 Hawk Films Ltd
Architecture
Automation
Continuous Delivery
Pipeline
aTEST
aSTAGING
aLIVE
aLIKE-LIVE
aTEST
aSTAGING
aLIVE
aLIKE-LIVE
"A good way to introduce continuous delivery is to model your current delivery process as a deployment pipeline, then examine this for bottlenecks,
opportunities for automation, and collaboration points."
Martin Fowler
"As a result, everybody in the delivery process gets two things: access to the things they need
when they need them, and visibility into the release process to improve feedback so
that bottlenecks can be identified, optimized, and removed."
Jez Humble & David Farley
aTEST
aSTAGING
aLIVE
aLIKE-LIVE
aTEST
aLIVE
aLIKE-LIVE
Architecture
Architecture
© Michael Coghlan, CC BY-SA 2.0© Michael Coghlan, CC BY-SA 2.0
aTEST
aLIVE
aLIKE-LIVE
aTEST
aLIVE
aLIKE-LIVE
Amazon Web Services
Tooling
klink
klink
Baking
klink
Baking App directory
klink
Baking App directory App deployment
klink
Baking App directory App deployment
App configuration
klink
Baking App directory App deployment
App configuration Infra configuration
mixradio/cluppet
klink
Baking App directory App deployment
App configuration Infra configuration
klink
Baking App directory App deployment
App configuration Infra configuration
aTEST
aSTAGING
aLIVE
aLIKE-LIVE
Repeatable
Fast
Repeatable
Fast
Flexible
Repeatable
Fast
Flexible
Repeatable
a a
a aPROD
aPOKE
aPROD
Deploying a service called 'heartbeat'
$ klink deploy heartbeat poke█
Deploying a service called 'heartbeat'
$ klink deploy heartbeat poke $ klink test heartbeat█
Deploying a service called 'heartbeat'
$ klink deploy heartbeat poke $ klink test heartbeat$ klink deploy heartbeat prod█
Deploying a service called 'heartbeat'
aPOKE
aPROD
aPOKE
aPROD
Automate judiciously and understand the costs, sometimes you can simplify instead.
Consider using a Continuous Delivery Pipeline as a transitional metaphor.
Automate judiciously and understand the costs, sometimes you can simplify instead.
Take a pragmatic view of risk, mitigate risks humanely.
Automate judiciously and understand the costs, sometimes you can simplify instead.
Consider using a Continuous Delivery Pipeline as a transitional metaphor.
@joelittlejohn