3 ms·

I have the sneaking suspicion that Amazon's Elastic Load Balancer is based on HAProxy (and has been tracking the 1.5 series in development for some time). Nothi

by jdub 12y ago

I have the sneaking suspicion that Amazon's Elastic Load Balancer is based on HAProxy (and has been tracking the 1.5 series in development for some time). Nothing particularly evidentiary, but it's a glass slipper that fits very snugly.

Rapzid 12y ago
I believe they use nginx. Traditionally ELB has been the most featureless LB's you'd ever encounter. That's in direct contrast with HAProxy. Truly a pain point with AWS IMO.
- jdub 12y ago
  ELB has features that nginx does not (health checks for one), and does not take advantage of many features that nginx does have. On the other hand, the feature set of HAProxy (1.5 branch, now "released") matches remarkably closely.
  - tachion 12y ago
    > ELB has features that nginx does not (health checks for one) Check out Tengine, a Nginx fork made by Alibaba guys ;)
- yarapavan 12y ago
  Mostly, HAProxy. In contrast, the AWS-clone Eucalyptus IaaS platform uses HAProxy for ELB functionality, mimicking AWS ELB functionality [1] [1] https://github.com/eucalyptus/architecture/blob/master/features/elb/3.3/elb-benchmark.wiki https://github.com/eucalyptus/architecture/blob/master/featu...
- wpietri 12y ago
  The AWS approach to things has been to launch things that are very basic and then add complexity only gradually and when they see steady demand for something. The flipside of that is that a) when they release something it, it's generally very solid, and b) what they support generally stays supported. That does mean that there are a lot of people who want AWS to support some particular feature. But having seen how featuritis can really ruin a code base, I'm glad they're conservative; I want my infrastructure to be very reliable.
lmz 12y ago
AWS is certainly on the list of "Who is using HAProxy" here: https://www.haproxy.com/ https://www.haproxy.com/