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.

1. Bursting the Pipeline
Evolving Continuous Delivery
at
@joelittlejohn

2. History

3. Dr. Strangelove © 1963 Hawk Films Ltd

4. Architecture

5. Automation

7. Continuous Delivery

9. Pipeline

10. a
TEST
a
STAGING
a
LIVE
a
LIKE-LIVE

11. a
TEST
a
STAGING
a
LIVE
a
LIKE-LIVE

14. "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

15. "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

16. a
TEST
a
STAGING
a
LIVE
a
LIKE-LIVE

17. a
TEST
a
LIVE
a
LIKE-LIVE

18. Architecture

19. Architecture

20. © Michael Coghlan, CC BY-SA 2.0
© Michael Coghlan, CC BY-SA 2.0

21. a
TEST
a
LIVE
a
LIKE-LIVE

22. a
TEST
a
LIVE
a
LIKE-LIVE

23. Amazon Web
Services

24. Tooling

33. klink

34. klink
Baking

35. klink
Baking App directory

36. klink
Baking App directory App deployment

37. klink
Baking App directory App deployment
App configuration

38. klink
Baking App directory App deployment
App configuration Infra configuration

39. mixradio/cluppet

40. klink
Baking App directory App deployment
App configuration Infra configuration

41. klink
Baking App directory App deployment
App configuration Infra configuration

42. a
TEST
a
STAGING
a
LIVE
a
LIKE-LIVE

43. Repeatable

44. Fast
Repeatable

45. Fast
Flexible
Repeatable

46. Fast
Flexible
Repeatable

48. a a

49. a a
PROD

50. a
POKE
a
PROD

51. Deploying a service called 'heartbeat'

52. $ klink deploy heartbeat poke█
Deploying a service called 'heartbeat'

53. $ klink deploy heartbeat poke
$ klink test heartbeat█
Deploying a service called 'heartbeat'

54. $ klink deploy heartbeat poke
$ klink test heartbeat
$ klink deploy heartbeat prod█
Deploying a service called 'heartbeat'

55. a
POKE
a
PROD

56. a
POKE
a
PROD

58. Automate judiciously and understand the costs,
sometimes you can simplify instead.

59. Consider using a Continuous Delivery Pipeline as a
transitional metaphor.
Automate judiciously and understand the costs,
sometimes you can simplify instead.

60. 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.

61. @joelittlejohn