We haven’t expected much from our load balancers in the past. And why should we? Traditional load balancers had a relatively simple job (e.g. distribute traffic, SSL, some content switching), and functioned relatively well. End of story.
I originally joined Avi Networks because I believed they had a robust, software-defined application delivery solution. It could do everything F5’s physical load balancers could do… or so I thought. After one week on the job, I’ve realized that Avi Networks only cuts costs by up to 70% only because you aren’t paying for hardware—hardware that can do a lot of things that Avi Networks just can’t do.
As a resident of New York I am fascinated by the history of this great city. The can-do attitude and swagger of “Gotham” but also the cultural diversity and complexity. As a technologist I am drawn to the mindboggling effort it takes to run an infrastructure necessary to support 8.4 million residents plus 1.5 million daily commuters who travel each day to the city for work. Urban life has always interested me. The photo above is a New York City street corner taken in 1887 only eleven years after Alexander Bell’s first long distance two-way phone call (between Cambridge and Boston). For the next 15 years both electric and telephonic wires would encase the city in an increasingly unorganized, dense web of entanglement. But progress marches forward. Legislation would be passed, money would be raised and the wires were soon moved underground only to be remembered in these old photographs.
This blog post originally appeared in Cisco's Data Center Blog site
Software load balancers are making a big splash in recent times driven by developer-centric and application-led initiatives. Adding to this growing space of excitement is the up and coming Avi Networks (a Gartner Cool Vendor in Enterprise Networking 2016) which makes load balancers cool again!
A minor change control has been approved, impacting only a small section of the network. However, the change is performed on shared network infrastructure such as firewalls or load balancers. Now comes implementation time, which is the ideal time for application usage but miserable for operators that value their weekends or evenings. Preparation is everything, the appropriate IT staff is on hand to conduct the change and the right business validators set to ensure success. Nothing unusual here and then…BAM! Something goes wrong. The NOC is inundated with calls and management system is lighting up like a Christmas tree.