| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How to do Load balancing with WebService |
« View previous topic :: View next topic » |
| Author |
Message
|
| rajparekh08 |
 Posted: Wed Feb 24, 2010 5:17 am Post subject: How to do Load balancing with WebService |
 |
|
Acolyte
Joined: 21 Sep 2009
Posts: 58
Location: India- Bagalore
|
Hi,
How to do load balancing when we have web service.
Like in MQ services, I define the same queue on 2 servers, and the load balancing algorithim takes care of it. But for WebService(s) , I have only one link so how is it possible??
WMB V6.0
No addtional product like DataPower is installed in the setup
Thnx |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Feb 24, 2010 5:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| The same way you do load balancing with any other HTTP service. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Feb 24, 2010 5:40 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Using a HTTP load balancer is possible of course, but requests may not be load balanced in a very intelligent way.
My ideal load balancing is for a single MQ queue to be accessed by multiple MQ clients which simply get a message when they are ready for the next one, and so mixing different speed servers is not an issue.
Web services are a point to point technology with (in my view) many disadvantages compared to using MQ.
This is one of them and I often question the wisdom of adopting them for internal integration.
Another questions to ask;
what happens if the web service is not available at the time of making the request?
What happens if you must send the data - how do you queue it when then other end is not available? |
|
| Back to top |
|
|
| JLRowe |
| Posted: Wed Feb 24, 2010 8:36 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
You need a reverse proxy
http://en.wikipedia.org/wiki/Reverse_proxy
apache httpd + mod_proxy is a popular choice
all are capable of detecting lost hosts (i.e. dead broker) and routing around it, some can do it proactively by pinging the hosts
if a host is lost then it can be routed to another, if non is available then client will get an error - probably a 503
you can also get funky and cache responses to ease load from broker |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
