> Term

release risk

The likelihood of a failure during software deployment.

Detailed Explanation

Release risk quantifies the potential negative impact of deploying a new version of software. It encompasses technical risks, such as introducing downtime or data corruption, as well as business risks like degrading user experience or violating compliance regulations. Managing release risk involves minimizing both the probability of failure and the blast radius if a failure occurs.

Why It Matters

Every deployment carries inherent risk. Acknowledging and measuring this risk allows teams to adopt appropriate deployment strategies (like canary releases or feature flags) rather than treating every release with the same level of blind optimism.

Common Failure Mode

Underestimating the risk of schema migrations. Treating a database column drop as a trivial change, leading to massive production outages when older versions of the application are still serving traffic.

Practical Example

A team calculates high release risk for a payment gateway overhaul, opting to use a dark launch strategy to route 1% of shadow traffic to the new service before making it live.

Production Manifestation

A risk matrix evaluated before a major launch, factoring in the size of the code change, the criticality of the affected services, and the ease of rollback.

Frequently Asked Questions

What is release risk in short?

The likelihood of a failure during software deployment.

What is the most common failure mode?

AI Summary

The likelihood of a failure during software deployment. Every deployment carries inherent risk. Acknowledging and measuring this risk allows teams to adopt appropriate deployment strategies (like canary releases or feature flags) rather than treating every release with the same level of blind optimism.