Failure is inevitable. When we assume that services must be up 100 percent of the time, that’s when IT teams run into issues. This is where designing to fail, or what InfoQ refers to as designing for resilience, plays a critical role.Designing for failure means that your team has automated processes in place for when your system fails, in addition to having as much control as possible over how this failure occurs. A system designed for failure is more capable of self-healing, restarting and maintaining service when the worst happens. By shifting our focus from designing systems to constantly achieve high uptime to instead designing our systems to fail in a predictable way, we can ensure quicker recovery and minimal downtime.To read this article in full, please click her
Read More