Rachel Laycock focuses on the architecture of an application, addressing patterns such as microservices and evolutionary architecture, which can speed up delivery.
Rebecca Parsons explores the relationship between evolutionary architecture, continuous delivery and microservices, focusing on how they support each other in the creation of complex systems.
Anna Shipman explains how the GOV.UK team implemented the DevOps culture – the people, the process, and the technical details of what tools they use and how they are integrated.
Arnaud Pflieger, Baeli Dimitri present their practices and tools: Octopus-a git branching model, no dedicated testers, no ops, Selenium, Zeno – a diff tool comparing production and staging code.
John Shaw discusses four pillars to DevOps: Environments, Deployment, Testing and People based on experiences developing financial systems for governmental clients.
Peter Niederwieser discusses building a continuous delivery pipeline using Gradle and Jenkins.
Sam Newman, Zhamak Dehghani make an introduction to microservice architectures, explaining why they are ideal for organizations that want to optimize for fast speed of change.
Jason Toy talks about the evolution and history of LinkedIn's release strategy.
Sangeeta Narayanan goes over how Netfix got to the current continuous delivery state, the lessons they learnt and the successes they enjoyed along the way.
Andy Vaughn gives attendees a case study of how changing the development model and release cycle of a 5 year old software product to continuous delivery greatly improved the product.
Lisa Van Gelder provides simple tips and tricks for improving delivery without investing lots of time up front creating complex deployment frameworks.
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.