John Sheehan presents choices – queues, proxies - helping a microservices architecture to stay robust and reliable, along with automation strategies allowing Runscope to deploy code 100 times a day.
Mike Bowler discusses CD, the build pipeline and version control practices and automated testing, exploring best practices and pitfalls, and making the deployment question a business decision.
Matthew Skelton shares his recent experience of helping many different organisations to evaluate and select tools to facilitate DevOps and Continuous Delivery.
Dave Farley discusses the problems raised by inefficient processes creating poor quality output, too late to capitalise on the expected business value, and proposes solutions to them.
Amy Phillips explains how the core principles can be used to drive process change and how their team removed many of the delays and frustrations from their release process.
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.
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.
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.