Should service orchestration functionality be included in ESB message flows?
Yes
0%
[ 0 ]
No
100%
[ 2 ]
Total Votes : 2
Author
Message
lancelotlinc
Posted: Wed Apr 14, 2010 6:52 am Post subject: Opinions:Orchestration & Proper Scoping of ESB Functiona
Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
Hi all! Happy Mothers Day.
Have a design query to float past you...
A common need when handling services is to manage context and execution sequence. This could be done through WebSphere Process Server or other products.
A tendancy I have observed with newer WebSphere Message Broker develoeprs is to try to integrate state management and service orchestration into Message Flows. While this is possible to do on a simplistic level (maybe two or three services), it can become unwieldy with more intricate business needs.
Please offer thoughts and comments on when it is optimum to push context management, state management, and service orchestration functions out of the ESB.
I would also be interested on some evangelistic tips to help newer ESB developers to realize the imperative of properly scoping the work the ESB does so that ESB concepts are maximized and pushing tasks not optimized for ESB functionality to some other entity besides WebSphere Message Broker. (ie. why reinvent the wheel inside the ESB when WPS could help?)
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum