Hello, I am opening this topic to know what your thoughts in the role of the broker in common SOA requirements.
One of the basic SOA usages is to creates abstraction layer between data provider applications and data consumer applications.
Normally we do this using Web Services over HTTP(S) with SOAP protocols. The common approach I see to address this implementations in webMethods is by not using the broker at any stage.
In the common approach architecture there are services to get data and services to expose data to consumers, the communication between those is done by direct invocation, top services close to business users invoke data services which can be in separated packages, but without recurring to the wMBroker at any stage.
In Web Services the communication is synchronous and that’s normally the excuse not to use the wMBroker, but it is well know that the broker supports synchronous communication.
My questions are do you see any advantage in calling creating an abstraction layer between top level services and bottom data services using wMBroker? (I can point one disadvantage -> performance).
What is your general experience with wMBroker in the SOA landscape do you have any samples were you really think the broker has a major advantage or it is really required?