- IIB or message broker has been on market for long time, it has been adopted by customers world widely. The introduction of WESB is very late.
- WESB caused confusion about IBM integration product stack. As a result, it hurt IBM sales of IBM integration products (to my believe).
- WESB is not as easy to use and not as flexible & versatile as IIB.
- If people would use WESB, why not open source Mule which is very similar to WESB in terms of platform. How did you justify spending much more for WESB instead of using the similar product Mule which is a lot cheaper?
middleware service, SOA, service oriented architecture, ESB, enterprise service bus, SOA governance, integration, messaging solutions, business process management, BPM, message queue, message broker, API management, datapower, ODM, solution architecture, enterprise architecture, application architecture, information technology.
Saturday, July 5, 2014
Finally, IBM Made a Smart Decision on Its Integration Product
A couple of months ago during IBM IMPACT conference 2014, IBM announced Integration Bus (IIB) v9 (formerly been known as WebSphere Message Broke) as one of IBM’s flagship integration products. As the same time, IBM asks its WESB (WebSphere Enterprise Service Bus) users to migrate to IIB. As an IBM technology solution professional, I have been working with a couple of IBM products including IIB and WESB. For long time, I was the person betting that WESB would not have much market. A few reasons made me believe so:
Labels:
ESB,
IBM integration bus,
IIB,
websphere enterprise service bus,
WESB
Subscribe to:
Posts (Atom)