An introduction to DevOps
By 2009, developers began to adopt Agile product development methods. They started with small deliveries in incremental cycles, gathering customer feedback and using it to inform future development cycles. They gradually created a product that their customers would want.
A bottleneck would soon form from delivering changes to the operations part of the organization. While rapid development of value is the priority of development teams, operations teams are charged with maintaining the stability of the environment. Anything that would diminish that stability would mean a potential loss of revenue. Typically, that meant seeing any new change as risky and allowing any changes to be released in specific maintenance windows. These windows only ended up increasing the risk of further downtime.
Changes would soon emerge. During the O’Reilly Velocity 2009 conference, John Allspaw and Paul Hammond of Flickr gave a talk titled 10+ Deploys a Day –...
