Operations | Monitoring | ITSM | DevOps | Cloud

We get it – incidents happen. What differentiates resilient teams from others is how they learn from them: using them as an opportunity to find the biggest improvements in how they work. Incident timelines are one of the most simple and effective tools available to you when it comes to learning from an incident. It’s vital that you ensure they’re accurate and useful, in order to make the biggest improvements after an incident.

Legendary race car driver Carroll Smith once said, "until we have established reliability, there is no sense at all in wasting time trying to make the thing go faster." Even though he was referring to cars, the same goes for technology: no amount of code optimization or new features can replace stable systems. Unfortunately, much like race cars, it's hard to know that a system is unreliable until it blows a tire, the brakes stop working, or the steering wheel comes off the column.

With the right load balancing in place, the demand of increasing web traffic can become manageable, but how do you determine which load balancing algorithm is best suited for your applications? Does the ease of use of static load balancing better suit the services you provide, or would your system benefit from a more complex and dynamic set of algorithms to maximize efficiency? In this blog post, we discuss what to consider when deciding on the right load-balancing algorithm.