Melody Meckfessel explores how Google's engineering teams use CD to build products and scale them, and how their strain of DevOps speeds launches and helps their engineering culture thrive.
Mitchell Hashimoto introduces Vagrant, Packer, Consul, Serf, explaining how they can help DevOps streamline the entire process from development through to production.
Jimmy Bogard takes a look at how Octopus enables continuous delivery and what it offers over standard tooling.
Simon Hildrew discusses the tools and processes used by The Guardian to create a continuous delivery pipeline.
Jevgeni Kabanov discusses the results of a research on a delivering software model, the tools involved and the model itself, concluding on what one can expect from using certain tools.
Derek Collison discusses some of the technologies and approaches for building a self-healing infrastructure: Intelligent layer 7 SDN with semantic awareness, self healing techniques, etc.
Dianne Marsh describes how Netflix' tooling, especially the continuous delivery system, allows developers to push the button for production deployment, and helps them to recover if necessary.
Avleen Vig discusses the changes Etsy has implemented to scale continuous deployments over the last 12 months, in both software and infrastructure.
Roy Rapoport discusses canary analysis deployment and observability patterns he believes that are generally useful, and talks about the difference between manual and automated canary analysis.
Baraa Basata introduces Ansible, comparing it with Chef and Capistrano and exploring automation principles: disposable servers, package management, and applying design principles to infrastructure.
Joakim Recht discusses how Tradeshift moved from manual deployment processes to automation and what this means in terms of organizational scalability, technology, transparency, and culture.
Nellwyn Thomas discusses how Etsy is using A/B testing, how Etsy's data-driven culture has evolved over time and how continuous delivery and big data can coexist.