Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm building a service-based web application. It consists of one primary rails app purely meant to handle requests, and a lot of other sinatra services running to actually process these requests.

I've decided to go with unicorn for the actual webserver for my rails app.

My dilemma is in picking the right stack to go with. I've read some great reviews about HAProxy's load balancing and I think that is the way to go for the long term. On the other hand, some people I know are also saying nginx would be good enough when I use it with unicorn.

At the moment, my entire system is going to reside on a single server. In the future, different servers might host different services.

Would I be introducing unnecessary overhead by introducing haproxy? How would I really gain from using HAproxy along with nginx?

share|improve this question
up vote 1 down vote accepted

Yep, haproxy's completely unnecessary. Unicorn does it's own "load balancing" between it's workers. When you move to needing multiple machines, you can use haproxy, but I strongly prefer an L3 solution such as IPVS.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.