You are signed in. Close

You are signed out. Close

Thank you. Your subscription has started. Close

Thank you. You will get an email when a new comic comes out. Close

We could not confirm your payment. If you paid, use the link "Sign in" at the bottom of the page. Close

Something went wrong on our side. Please try again in a moment. Close

Previous episode Staging vs production: why an app is tested on a copy first

How CI/CD works: why releasing code every day is safer than once a month

Continuous delivery: why a release should be one boring button

In 2012, a trading firm copied new code onto eight servers by hand and missed one. When the market opened, it lost more than $460 million in about 45 minutes. What continuous delivery changes in the last step before production.

  1. 1 In the last days of July 2012, a technician at the trading firm Knight Capital copied new code onto eight servers by hand, and missed one. On 1 August, that server still ran old code: it sent millions of orders to the market, and in about 45 minutes the firm lost more than $460 million.end of Julytechnician1 Augustorders, orders, orders45 min

    In the last days of July 2012, a technician at the trading firm Knight Capital copied new code onto eight servers by hand, and missed one. On 1 August, that server still ran old code: it sent millions of orders to the market, and in about 45 minutes the firm lost more than $460 million.

  2. 2 Rono's list of hand steps holds the same kind of risk, every single time: one step skipped on one server, late at night, by a tired person.Rono1. copy files2. restart3. checkproduction

    Rono's list of hand steps holds the same kind of risk, every single time: one step skipped on one server, late at night, by a tired person.

The rest of this episode is for subscribers

Subscribe to read every premium episode. You can cancel when you want.

Paid yearly: $99 instead of $119.88

Next episode Continuous deployment: what changes when nobody presses the button

Share this comic

More comics