Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Reducing risk with continuous delivery

Reducing risk with continuous delivery

What is continuous delivery and how does it reduce risk with case studies.

This was a lunch time talk at Pivotal (http://www.meetup.com/Pivotal-Labs-Tech-Talks/)

Joel Chippindale

November 05, 2014
Tweet

More Decks by Joel Chippindale

Other Decks in Programming

Transcript

  1. Reducing risk with continuous
    delivery
    BY JOEL CHIPPINDALE - NOVEMBER 2014

    View full-size slide

  2. A story about FutureLearn

    View full-size slide

  3. How many of you work in continuous
    delivery environments?

    View full-size slide

  4. How do you explain the benefits?

    View full-size slide

  5. What is continuous delivery?

    View full-size slide

  6. What is continuous deployment?

    View full-size slide

  7. What is deployment?

    View full-size slide

  8. All the work required to make a
    new feature available to users

    View full-size slide

  9. Release based deployment

    View full-size slide

  10. Benefits
    • QA have time to check each release
    before it goes live
    • Marketing can announce releases
    • Defined process sounds reliable

    View full-size slide

  11. But what happens when
    something goes wrong?

    View full-size slide

  12. • Bugs found in QA can delay ALL features.
    • Features may miss the ‘release window’
    • How are bugs fixed that are found AFTER QA?
    • Scheduled downtime?

    View full-size slide

  13. Big releases are complicated
    releases

    View full-size slide

  14. The more complicated the release the greater
    the chance that something will go wrong

    View full-size slide

  15. Continuous deployment

    View full-size slide

  16. • Bugs found in QA can delay ALL features.
    • Features may miss the ‘release window’
    • How are bugs fixed that are found AFTER QA?
    • Scheduled downtime?

    View full-size slide

  17. Benefits
    • Features and bug fixes available as soon
    as they are ready
    • Most deployments can be made with
    zero downtime

    View full-size slide

  18. Continuous deployment
    vs.
    Continuous delivery

    View full-size slide

  19. Case study 1: Etsy

    View full-size slide

  20. More than 1 billion dollars worth
    of sales made on Etsy in 2012
    Source: Contniuous deployment at Etsy

    View full-size slide

  21. How often do Etsy deploy code?

    View full-size slide

  22. 25+ times per day

    View full-size slide

  23. Who can deploy code at Etsy?

    View full-size slide

  24. Automated tests

    View full-size slide

  25. Fast and easy deployments

    View full-size slide

  26. Constant monitoring

    View full-size slide

  27. Continual bug fixing

    View full-size slide

  28. …and gradual role out of
    features

    View full-size slide

  29. Case study 2: gov.uk

    View full-size slide

  30. 50 million visits a month
    Source: GDS blog

    View full-size slide

  31. Several deployments a day,
    thousands since launch

    View full-size slide

  32. Automated tests

    View full-size slide

  33. Fast and easy deployments

    View full-size slide

  34. Constant monitoring

    View full-size slide

  35. …and smoke tests

    View full-size slide

  36. Case study 3: FutureLearn

    View full-size slide

  37. 700,000 learners

    View full-size slide

  38. Average of 3 deployments every
    working day

    View full-size slide

  39. Automated tests

    View full-size slide

  40. Fast and easy deployments

    View full-size slide

  41. Constant monitoring

    View full-size slide

  42. Continual QA and bug fixing

    View full-size slide

  43. …beyond Etsy, gov.uk and
    FutureLearn

    View full-size slide

  44. Continuous delivery works well
    with

    View full-size slide

  45. Automated tests

    View full-size slide

  46. Fast and easy deployments

    View full-size slide

  47. Constant monitoring

    View full-size slide

  48. Continual bug fixing

    View full-size slide

  49. These are good practices for
    EVERY project

    View full-size slide

  50. Continuous delivery:
    Reduce risk by delivering small
    changes often and monitoring
    feedback

    View full-size slide

  51. Questions?
    @joelchippindale
    [email protected]
    about.futurelearn.com/blog/

    View full-size slide