Just over a year ago, Pearson, who published Continuous Delivery, approached Martin Fowler and I with a proposal to do a series of videos on the topic of continuous delivery. We filmed a bunch of material for these videos, but then both Martin and then I dropped out of the project due to other commitments. Pearson are working on putting the material together - we're planning to donate the proceeds to Black Girls Code - but in the meantime (and in the spirit of continuous delivery) we're going to post some of the material in low-def format for your viewing pleasure.
The videos we'll be posting are interviews with Jesse Robbins, Eric Ries, Elizabeth Hendrickson and John Allspaw. This week, it's Jesse Robbins. Here's his bio:
Jesse Robbins is Co-founder and Chief Community Officer of Opscode, the leader in Cloud Infrastructure Automation. Jesse is a widely recognized expert in Infrastructure, Web Operations, and Emergency Management. Jesse was a founding chair of the Velocity Web Performance & Operations Conference, co-editor of the Web Operations book, and is a contributor to the O'Reilly Radar blog. Prior to founding Opscode as CEO in 2008, he worked at Amazon.com with the title of "Master of Disaster" where he was responsible for Website Availability for every property bearing the Amazon brand.
In the video, Jesse answers the following questions:
Devops - what's the big deal?
What do operations teams need to change to enable continuous delivery, and how do they go about it?
How can you measure how good you are at continuous delivery?
Tell us a little bit about Chef. What is infrastructure as code? Why is it important?
That sounds a lot like mainframes. Are we seeing a return to that model?
What's the role of operations in this model?
Can you tell us a bit about how Amazon Web Services came into being?
What are some good practices for architecting cloud-based systems?