[ad_1Companies around the world and across many industries have felt the pressure to release faster, yet they struggle to do so safely and reliably that doesn’t compromise user trust.
Many of these companies think there’s a dichotomy between whether you can move fast or increase value.
“I think the move fast and break things got a bad rap. It’s kind of horrifying to think, Hey, a developer that I’m not even talking to could suddenly blow up my entire customer base without all these gates,” said Edith Harbaugh, the CEO of LaunchDarkly, during a recent SD Times Live! tech talk.
However, releasing slower today could make the software more unsafe, according to Harbaugh.
“If you’re doing the old software releases of 20 years ago where you do a release every year, every release has so much heft, weight, and gravity behind it,” said Harbaugh.
The releases are heavy in technical complexity, requiring developers to check all of these different branches and features. Still, they are also risky from a business perspective because the value planned a year ago might not even be relevant anymore. This could cause a significant release to flop when out in the field.
Both speed and value are mutually possible with the proper distributed architectures and guardrails that limit the blast radius. One such method for safer deployments is canary deployments, limiting the blast radius from 100% of the user base and having it down to where it may affect 1% of the most progressive users.
The canaries are typically an engineering activity and feature flags – which are a core part of this activity – help unlock value way up in the stack, according to DROdio, the CEO of Armory.