IBM WebSphere MQ WCF Channels comparison update
Wrote a lot about the IBM WebSphere MQ WCF Channels in the past. Check out my original post and an update on that one.
What changed in the meantime is that Microsoft added backout queue support to their channel in a hotfix. My comparison table now looks like this:
|
|
IBM
|
HIS2009
|
HIS2010
|
|
Fire-and-forget (oneway) client
|
+
|
+
|
+
|
|
Fire-and-forget (oneway) service
|
+
|
+
|
+
|
|
Request-reply client
|
+
|
-
|
+
|
|
Request-reply service
|
+
|
-
|
+
|
|
Local transactions
|
+
|
-
|
+
|
|
Distributed transactions (DTC)
|
-
|
+
|
+
|
|
Client side transactions (DTC)
|
-
|
+
|
+
|
|
Backout queue support
|
+
|
-
|
+
|
|
Message format
|
-
|
+
|
+
|
AppFabric support / IIS Hosting
(WAS listener for IIS7) |
-
|
-
|
+
|
|
Works with .NET 3.x
|
+
|
+
|
-
|
|
Works with .NET 4.0
|
+
|
+
|
+
|
|
WMQ6 support
|
-
|
+
|
+
|
|
WMQ7 support
|
+
|
+
|
+
|
|
Sample code
|
+
|
+
|
+
|
|
Documentation
|
+
|
-
|
-
|
|
Licensing
|
+
|
-
|
-
|
Conclusion
We'll consider starting to use the HIS channel for services only. Hosting services with the HIS channel can be interesting due to support for AppFabric which can save development and maintenance time. For client side we’ll probably stay on the IBM channel anyway due to the licensing costs of the Microsoft channel.