Suppose that a hypotetical webapp keeps one connections per user (eg: chat app using comet, long pooling, etc...). How can i load balance such thing to scale beyond the connection limit of a single machine (C10[0]K) ?

I can see round robin DNS as a solution, would like to know what else would be possible...

link|improve this question
1  
Are there not a million dupes of this question? – Lightness Races in Orbit May 24 '11 at 14:46
I also thought so, but couldn't find... could you point some? – Julio Faerman May 25 '11 at 13:16
Look to the right. – Lightness Races in Orbit May 25 '11 at 13:18
feedback

migrated from stackoverflow.com May 24 '11 at 16:16

This question came from our site for professional and enthusiast programmers.

2 Answers

The far extreme of this is Geographic DNS distributing discrete round-robin IP address pools which in turn point to clustered hardware load-balancers using Virtual IP to handle failover. I say hardware since the big hardware load-balancers are designed for truly massive connection-counts.

link|improve this answer
That's what i think too... do you have an idea of how much "massive" this count is? – Julio Faerman May 25 '11 at 13:17
feedback

dns load balancing will do but you don't have much control over it - better use a load balancer.

link|improve this answer
The problem is what to do when you exceed the capacity of a single load balancer. – Julio Faerman May 25 '11 at 13:16
have two or more load balancers handling the traffic, these can as well be mixed with dns round robin – silviud May 25 '11 at 15:01
feedback

Your Answer

 
or
required, but never shown

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