What are the disadvantages of MSMQ over MQ Series, for communication with a Web service?
One of the primary disadvantages of MSMQ is that MSMQ is a Windows-only Messaging product. It also doesn't have any native support for JMS (Java Messaging Service) and you would need a JMS-Bridge to get JMS Clients to communicate with the MSMQ broker.
IBM MQSeries on the other hand is supported on multiple platforms and can be accessed by different clients (C, Java, JMS, Perl) and therefore is better suited for heterogeneous environments like that of a large enterprise.
Web services are commonly implemented as part of a broader move towards a Service Oriented Architecture (SOA). The fundamental concept within an SOA design is the "loosely-coupled reusability of business components"; simply choosing MSMQ or MQ Series raise serious concerns regarding reusability. A system is not truly loosely-coupled with reusable components unless individual components can be made to communicate without having to be modified. Large organizations will have many components that prefer to communicate via MQ however they are unlikely to have all the components taking part in their SOA be capable of communicating via MQ. The best way to address this issue is to deploy Web Service Management (WSM) software that is capable of bridging across multiple transports while securing your XML messages all the way from the client to the Web services.
Dig Deeper on Service orchestration
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.