Every deployment carries risks, but smarter devops teams know how to balance speed with preparedness to avoid deployment horrors.
However, these elite performers also report a 5% change failure rate, which may be acceptable for applications that aren't mission-critical or deployments triggered during low-usage periods.
CrowdStrike recently made headlines with a failed deployment impacting 8.5 million Microsoft Windows computers, causing nearly 10,000 flight cancellations worldwide.
It might be time for devops organizations to rethink their deployment strategies. When are frequent releases too risky, and how should teams evaluate the risks of a change?
Collection
[
|
...
]