Building network automation solutions

9 module online course

Start now!

Scale-Out Load Balancing with OpenFlow

When OpenFlow was still fresh and exciting, someone made quite a name for himself by proposing a global load-balancing solution that would install per-session OpenFlow entries in every core switch around the world. Clearly a great idea, mimicking the best experiences we had with ATM SVCs.

Meanwhile some people started using OpenFlow in real-life networks for coarse-grained load balancing that improves the scalability of stateful network services. For more details, watch the video recorded during the Real Life OpenFlow-based SDN Use Cases webinar.

We migrated our blog a few days ago, and the commenting functionality is not there yet. In the meantime enjoy the older comments, or find our content on LinkedIn and comment there.


  1. There are switches that can do consistent hashing, e.g. Broadcom:

    In this case, upon failure of a switch only 1/N of flows get rehashed ( i.e. the ones that were hashing to the failed LB ).

    In case of a web site, couldn't you simply use a set of HTTP redirect based load balancers?

    1. HTTP redirects don't give you high availability. If a particular back-end server fails, all clients redirected to it lose service.