Chapter 5. Infrastructure As Code

Adam Jacob

YOU’RE SITTING AT HOME, WATCHING A MOVIE AND EATING POPCORN, with your feet up and the family gathered around you. The phone rings—it’s your on-call system administrator.

“The datacenter has been hit by a tornado—it ripped right through our cage. What do we do?”

Once you get over the obvious answer,[1] you start running down the list:

  1. Pause the movie.

  2. Sign up for an account with a cloud computing provider, to replace the raw computing, network, and storage resources you have lost.

  3. Start uploading/downloading the off-site backups of your customer and application data to the new infrastructure.

  4. Provision enough servers to bring the company back online, assigning an appropriate role to each new server resource (“web server,” “database server,” “monitoring server,” etc.).

  5. Change your DNS to point to your new infrastructure, with a “we got hit by a tornado” page.

  6. Restore the customer and application data.

  7. Remove the “we got hit by a tornado” page.

  8. Finish the movie.

One hour and forty-five minutes later, you’ve gone from business-ending natural disaster to finishing your family movie night. How did you do it? You built the original infrastructure as code: a series of interconnected services, relying on each other to bring each component of the system into the proper running state. All you had to do was apply that code to new resources and restore the application data, and you knew you would get the entire business back up and running from scratch.

This ...

Get Web Operations now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.