Originally Posted by FightThisPatent

strictly HTTP. round robin can be the simplest method as long as it knows when a server goes down to stop routing to that server.

not looking for DNS round robin. wanting the balancer to balance between internal IPs so that I can have N number of database servers that receive http/php for api calls to the database, rather than direct db calls from my app.

so the webserver (ie. t3report.com) receives a user request for data. the server side makes http/api call to the rack (behind a firewall). the machine (ip) that it connects to is currently a server that then connects to the db to get the data.

in the new infrastructure, the webserver (t3report.com) makes http/api calls to the load balancer, from which it tunnels to the backend server, passing the http/api request, and data comes back.


Fight the unbalanced!