All Systems Fail*
All Systems Fail*
*Yes, all. Why failure is such a great way to learn and develop software.
Join the DZone community and get the full member experience.
Join For FreeLearn how integrating security into DevOps to deliver "DevSecOps" requires changing mindsets, processes and technology.
Vince Lombardi once said, "It's not whether you get knocked down, it's whether you get up." But in today's world of high velocity development and release practices, it's also about how fast you can get up.
Today, we are seeing more news about sites from major online retailers and service providers like HP, Target, PayPal, and Neiman Marcus going down. High site traffic, poor configurations, scalable architectures, and well planned recovery practices all come into play.
But the best organizations have been failing repeatedly for some time now...on purpose. Organizations like Amazon, Google and Netflix practice regularly for application, system and site outages. In fact, Netflix has baked continuous failures into its operations through an internally developed Simian Army. While it might seem unconventional at first, failing all the time allows them to succeed.
Our CTO here at Sonatype, Josh Corman, often reminds us that "All Systems Fail*". For those that take this to heart and prepare for the inevitable, they can be better prepared to recover. In fact, for the best prepared, recovery can be so seamless, it is a continuous part of their operations.
Learn how enterprises are using tools to automate security in their DevOps toolchain with these DevSecOps Reference Architectures.
Like This Article? Read More From DZone
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}