| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Webservice vs MQ |
« View previous topic :: View next topic » |
| Author |
Message
|
| kspranava |
 Posted: Mon Nov 13, 2006 2:02 am Post subject: Webservice vs MQ |
 |
|
Centurion
Joined: 27 Apr 2003
Posts: 124
|
Hi All,
We need to send a msg to broker from .Net application. Two possible ways to do so,
1) Webservice: invoking msgflow using HTTP nodes
2) Putting message in a MQ queue and msgflow picking it up using
MQInput node.
But the problem is, .Net application is not MQ enabled and hence need
change; at the same time facility for webservices is already available. Is there any advantage or disadvantage of using web services?
Broker: WMB v6 in Solaris
Thanks in advance,
-kspranava |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Nov 13, 2006 3:33 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
http is for synchronous communications, MQ will support asynchronous communication... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Nov 13, 2006 3:41 am Post subject: Re: Webservice vs MQ |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| kspranava wrote: |
. Is there any advantage or disadvantage of using web services?
|
It's kinda the same arguement (in reverse) of the "do we buy MQ" question; if we've got TCP/IP links with socket-enabled programs, ftp and so forth why do we need to buy MQ & change a lot of code?
The answer is reliant on your individual requirements, how much you value decoupling, how much time you have to change code, etc, etc. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Nov 13, 2006 4:04 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
|
| Back to top |
|
|
| msukup |
| Posted: Mon Nov 13, 2006 7:15 pm Post subject: |
|
|
Acolyte
Joined: 11 Feb 2002
Posts: 56
|
if you want to increase the quality of service, MQSeries will enhance (or assure) reliability. HTTP is inherently unreliable, and we have had our problems maintaining connections over it. if your data is at all transactional or important in nature, the MQ solution is very attractive, especially if you already have a message broker.
naturally, you have to weigh that against how invasive a change in your existing application would be. if it's not easily changed, then the http protocol in msg broker is there for you to take advantage of. decisions!! |
|
| Back to top |
|
|
| kspranava |
| Posted: Wed Nov 15, 2006 1:01 am Post subject: |
|
|
Centurion
Joined: 27 Apr 2003
Posts: 124
|
Hi All,
Thanks a lot for your inputs.
-kspranava |
|
| 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
|
|
|
|
