Anti-Fragile DevOps

With need for rapid changes in our apps, making change hard since change is risky — is flawed.  Massive changes with rigorous change management approvals might exhibit no visible risks but could eventually lead to massive blowups catching everyone off guards.   Introducing massive changes introduce new operations vulnerabilities with each release, due to dependence upon manual process steps.

The solution is to make changes small in scope, stress the deployment process so that the release process becomes a boring and a low risk task with a heavy reliance on automation. It requires organizational acceptance to rollback the changes if an issue arises, but since the scope of change is small it becomes more manageable. This approach over time makes the product more robust & less susceptible to massive blowups.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: