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 Slide

  2. A story about FutureLearn

    View Slide

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

    View Slide

  4. How do you explain the benefits?

    View Slide

  5. What is continuous delivery?

    View Slide

  6. What is continuous deployment?

    View Slide

  7. What is deployment?

    View Slide

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

    View Slide

  9. Release based deployment

    View Slide

  10. Process

    View Slide

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

    View Slide

  12. But what happens when
    something goes wrong?

    View Slide

  13. • 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 Slide

  14. Big releases are complicated
    releases

    View Slide

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

    View Slide

  16. Continuous deployment

    View Slide

  17. Process

    View Slide

  18. • 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 Slide

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

    View Slide

  20. Continuous deployment
    vs.
    Continuous delivery

    View Slide

  21. Case study 1: Etsy

    View Slide

  22. View Slide

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

    View Slide

  24. How often do Etsy deploy code?

    View Slide

  25. 25+ times per day

    View Slide

  26. Who can deploy code at Etsy?

    View Slide

  27. EVERYONE

    View Slide

  28. Automated tests

    View Slide

  29. Fast and easy deployments

    View Slide

  30. Constant monitoring

    View Slide

  31. Continual bug fixing

    View Slide

  32. …and gradual role out of
    features

    View Slide

  33. Case study 2: gov.uk

    View Slide

  34. View Slide

  35. 50 million visits a month
    Source: GDS blog

    View Slide

  36. Several deployments a day,
    thousands since launch

    View Slide

  37. Automated tests

    View Slide

  38. Fast and easy deployments

    View Slide

  39. Constant monitoring

    View Slide

  40. …and smoke tests

    View Slide

  41. Case study 3: FutureLearn

    View Slide

  42. View Slide

  43. 700,000 learners

    View Slide

  44. Average of 3 deployments every
    working day

    View Slide

  45. Automated tests

    View Slide

  46. Fast and easy deployments

    View Slide

  47. Constant monitoring

    View Slide

  48. Continual QA and bug fixing

    View Slide

  49. …beyond Etsy, gov.uk and
    FutureLearn

    View Slide

  50. Amazon

    View Slide

  51. Google

    View Slide

  52. Facebook

    View Slide

  53. Continuous delivery works well
    with

    View Slide

  54. Automated tests

    View Slide

  55. Fast and easy deployments

    View Slide

  56. Constant monitoring

    View Slide

  57. Continual bug fixing

    View Slide

  58. These are good practices for
    EVERY project

    View Slide

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

    View Slide

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

    View Slide