Load balancers are a cornerstone of any big computing application. By spraying traffic across lots of servers, they let companies turn many unreliable machines into one reliable service. But that service has a lot of moving parts, and sometimes they break. If it keeps happening, it may signal that a new class of networking device is needed for the demands of cloud computing.
According to Amazon’s Web Services Developer Connection, a load balancer was deployed in its S3 storage service on June 20, and removed two days later. During that time, it was corrupting bytes of data sent to the S3 storage service when under load.
This isn’t the first time load balancers have been implicated in an outage at Amazon. At O’Reilly’s Velocity conference, conference co-chair Jesse Robbins talked about a “redundant array of inexpensive data centers” as the basis for tomorrow’s computing platforms. Load balancing is what makes this possible.
Storing data in a server is a tried and tested process. We’ve had decades to optimize the way we store and retrieve data, with standards like iSCSI and IDE proven out worldwide. And RAID is pretty reliable these days.
But the cloud’s still figuring out storage. There are competing models: S3, SimpleDB, BigTable and so on. And with more and more applications relying on S3 for their data, outages are bound to be visible and public.
The cloud model puts increased pressure on networking and server equipment, and on vendors to make their components reliable. Load balancers built for enterprise data centers may not be suited for the cloud, just as domestic power generators wouldn’t work for utility companies. This may be one reason Google is reputed to be building its own switches.
Expect clouds to require significantly different kinds of networking equipment. It’s either an opportunity for networking vendors like Cisco and Juniper, or a huge threat to them.