The research the community asks of you is the research to answer your question, not to ask it. I freely accept that you've done enough research to find out what load-balancing options are generally available, but if you hadn't done that I suspect the question would look like "I need to know about load balancers, please help me" and would already have been closed.

What we're looking for you to do is research towards answering the question as asked, so that we don't duplicate work you've already done. If you haven't done any such work, then a downvote may be appropriate.

But as others have already noted, the question as written could have a whole book by way of answer - see, eg, http://shop.oreilly.com/product/9780596000509.do - and is thus almost certainly too broad for SF. Our guidelines are fairly clear on that:

Your questions should be reasonably scoped. If you can imagine an entire book that answers your question, you’re asking too much.

The research the community asks of you is the research to answer your question, not to ask it. I freely accept that you've done enough research to find out what load-balancing options are generally available, but if you hadn't done that I suspect the question would look like "I need to know about load balancers, please help me" and would already have been closed.

What we're looking for you to do is research towards answering the question as asked, so that we don't duplicate work you've already done. If you haven't done any such work, then a downvote may be appropriate.

But as others have already noted, the question as written could have a whole book by way of answer - see, eg, http://shop.oreilly.com/product/9780596000509.do - and is thus almost certainly too broad for SF. Our guidelines are fairly clear on that:

Your questions should be reasonably scoped. If you can imagine an entire book that answers your question, you’re asking too much.