Is it about delivering at scale
For a long time I struggled with why I should recommend a customer pay to migrate a steady-state workload to any type of cloud environment (private, public, hybrid). After all, it doesn't see the spikes mentioned in this article, there's a nominal % growth year over year, the operations team have a complete Runbook for operating the system through any type of disaster. There's so many other areas where IT could more effectively spend their money than to take this workload and migrate it to a cloud environment.
What convinced me of the importance of taking this step was listening to Randy Bias at a recent DevOps Meetup in Chicago. I've paraphrased it so much, I don't remember his original statement, but for me it works out to there's a major fundamental benefit from delivering 5 9's software running on 2 9's hardware versus building 5 9's in hardware.
And there it is, the gold at the end of the rainbow for DevOps.
The mission that could only effectively be met by development & operations working hand in hand as an effective team with appropriate controls and communications. The value proposition is significant. If you don't believe, read the stories coming out of Google, Facebook & Twitter. Resiliant software designed to operate in the face of hardware failure with no/minimal loss of data running on commodity hardware that can be continually be expanded without requiring maintenace windows or reconfiguration, operates across geographic distances so that loss of an entire facility constitutes only a minor disruption in service all done at a fraction of what it would cost to operate using traditional enterprise hardware alternatives.