3 ms·
It's amusing to see that they've reinvented the "active health checks" wheel for their system, because HAProxy [1] does this out of the box. Side-note/rant: I
by jaytaylor 14y ago
It's amusing to see that they've reinvented the "active health checks" wheel for their system, because HAProxy [1] does this out of the box.
Side-note/rant: I am always surprised that HAProxy doesn't get more attention on hackernews, because it is an incredibly powerful tool. IMO, it is definitely one of the biggest technical unsung heroes I'm presently aware of.
[1] http://haproxy.1wt.eu http://haproxy.1wt.eu
- shykes 14y ago(dotCloud employee here) We are very much aware of HAProxy, love it, and would have been very happy to use it. For the majority of use cases we would probably recommend it over Hipache, simply because it's more proven. However, our particular use case involves a) a very large number of vhosts, and b) a highly dynamic topology where backends are added and removed very frequently. In this setup, instrumenting a cluster of HAProxy (or nginx) boxes basically means re-generating and reloading multi-megabyte configuration files across dozens of machines, several times per second. It's what we did before Hipache, and it was painful. Compared to that, implementing active health checks was a small price to pay.
- jaytaylor 14y agoThank you for clarifying