The latest News and Information on DevOps, CI/CD, Automation and related technologies.
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.
When it comes to building reliable and scalable software, few organizations have as much authority and expertise as Google. Their Site Reliability Engineering Handbook, first published in 2016, details their practices to maintain reliability as Google scaled. But when you have over a million servers running thousands of services across more than twenty data centers, how do you monitor them in a consistent, logical, and relevant way?