Progressive delivery limits the blast radius of code releases
Progressive delivery lessens the risk from releasing new code by limiting the ‘blast radius’, or set of users exposed to a bad change before it is detected.
Split makes it easy to practice progressive delivery through feature feature, user targeting, error alerting, and A/B testing.
What is progressive delivery?
Progressive delivery is an approach to incrementally exposing changes to users. First roll out a new feature to the team building it, then to QA, then to all employees, then to beta testers, then to increasing proportions of users.
It is an extension of continuous delivery, offering a lower risk release pattern. By gradually rolling out, development teams can reduce the risk of user-facing bugs or performance problems, the ‘blast radius’, during a release.
Progressive delivery case studies
Progressive delivery with controlled rollouts
Split has the key elements necessary for safe, reliable progressive delivery. Toggle on or off feature flags to set the appropriate exposure for individual features. Target them to specific users or user segments during your progressive roll out.
Split pairs feature flags with operational and customer data, monitoring in real time the rollout of new code. This reduces the number of users—the size of the blast radius—that are exposed to a bad feature before you detect a bad feature and turn it off.
Progressively roll out features today
Split has all the tools you need for progressive delivery: feature flags, user targeting, alerting, and an instant-off switch.