Progressive exposure is one of the important practices in DevOps. In a nutshell, progressive exposure is the process of slowly deploying to select sections as a means of testing, rather than universally.

The idea of progressive exposure is that, unlike in the past, when a new deployment would instantly become available to everyone, we want to minimise the blast radius. We want to allow the new deployment to go live, but to go live in a contained environment, where only a few people have access in production, and then as we validate that new deployment, we have more and more and more people exposed.

Next, we will move on to our final topic which is continuous learning.

Join the discussion

What are some methods or metrics we could use to determine our pools for progressive exposure? Can you suggest some ways in which popular applications currently employ this tactic?

Use the discussion section below and let us know your thoughts. Try to respond to at least one other post and once you’re happy with your contribution, click the Mark as complete button to check the step off, then you can move to the next step.