A table showing the relative strengths of the service integration and WebSphere MQ messaging platforms. If your enterprise is not already an established user of either WebSphere Application Server or WebSphere MQ, use this table to help you decide which product best fits your emerging needs.
Service integration (the default messaging provider for WebSphere Application Server) | WebSphere MQ |
---|---|
Close integration with WebSphere Application Server - good if focus is on the Java Platform, Enterprise Edition (Java EE) | Connect everything: very heterogeneous environment |
Multiple languages through XMS clients; multiple platforms | Multiple languages and platforms |
Single process; pure Java implementation | |
Good performance for both persistent and non-persistent messages for JMS (better than WebSphere MQ JMS) | Supports JMS and non-JMS messaging interfaces. Good performance for non-JMS applications (significantly outperforms JMS). |
Maximum message size ~40MB on 32-bit system (subject to heap usage) | Large messages (100MB) |
Tight integration with service integration bus Web services | Natural fit if using WebSphere Message Brokers |
Messaging is included in a single administrative model for WebSphere Application Server, WebSphere Enterprise Service Bus, and WebSphere Process Server. | Integrates existing infrastructure and applications (for example CICS) |
Service integration bus clustering is integrated with WebSphere Application Server clustering for high availability and scalability. | Supports WebSphere MQ clustering, which provides selective parallelism of clustered queues. |
Has many Independent Software Vendor (ISV) tools. |