Development PracticesConference50min
How we scaled Continuous Delivery across 1000s of Developers and 100s of applications
This talk presents a scalable, contract-based approach to standardizing software delivery pipelines, fostering alignment across development, operations, and security. It covers key technical foundations for Continuous Delivery, common anti-patterns to avoid, and practical patterns to improve reliability, autonomy, and flow in platforms supporting diverse technologies and large developer teams.
Christopher BateyCore Engineering Consulting Group
talkDetail.whenAndWhere
Wednesday, October 8, 17:50-18:40
Room 3
Many organisations attempt to standardise their path to production. Most fall short. What starts as a push for consistency often results in brittle pipelines, increasing exceptions, and developers working around the platform rather than with it.
This talk shares a practical and proven approach that has enabled Continuous Delivery adoption at scale across thousands of developers and hundreds of services in environments with a wide range of technologies and constraints.
We will explore how treating the Path to Production as a Contract between developers, operations, security, and change creates alignment and accountability. We will also walk through five common anti-patterns that quietly undermine adoption, and how to avoid them before they become systemic.
On the technical side, we will cover:
If you are building a platform for software delivery, this talk will offer patterns, pitfalls, and principles that work in practice.
This talk shares a practical and proven approach that has enabled Continuous Delivery adoption at scale across thousands of developers and hundreds of services in environments with a wide range of technologies and constraints.
We will explore how treating the Path to Production as a Contract between developers, operations, security, and change creates alignment and accountability. We will also walk through five common anti-patterns that quietly undermine adoption, and how to avoid them before they become systemic.
On the technical side, we will cover:
- Why DIVAs (Deployable, Immutable, Versioned Artifacts) are foundational for Continuous Delivery
- How the right delivery unit design reduces blast radius and improves autonomy
- The difference between CI validation and promotion, and how separating them improves flow
- How to match the testing strategy to delivery goals without adding delay
- What application architecture needs to provide to support reliable and scalable delivery
If you are building a platform for software delivery, this talk will offer patterns, pitfalls, and principles that work in practice.
Christopher Batey
Over 20 years Christopher has spent time in most areas of software delivery, product development, JVM library development (concurrency/distributed systems), Infrastructure engineering, architecture & system design and most recently Platform Engineering. He has a passion for speed and stability. Focusing on what we need to do next to speed up the software delivery lifecycle.
Over the years he’s contributed to many open source projects including Akka & Kubernetes.
Over the years he’s contributed to many open source projects including Akka & Kubernetes.
talkDetail.transcript.loginToSeeTakeaways
talkDetail.transcript.loginToSeeInsights
comments.speakerNotEnabledComments