Prior to emergence of Web services standards, SOAP, WSDL and more recently BPEL4WS and WS-T, virtually all systems for coordinating asyncronous activities were implemented as standalone solutions. This required creating multiple layers of heavy-duty infrastructure, with little or no concern for a coherent application model.
An alternative approach, based on delivering Web service orchestration on top of an application server, can provide the following advantages:
(1) Increasingly, integration with existing components and services is a development task as part of building an application rather than integration being the application itself (aka system glue). Delivering an orchestration solution on top of J2EE is less intrusive and can also provide native J2EE support for other application components. It also integrates seamlessly into the overall application development lifecycle.
(2) J2EE already provides a sound application model, based on MVC (model-view-controller) architecture. Extending capabilities from this architecture while preserving the application model should result in better utilization of developer skills, more consistent application designs and implementations that are easier to maintain and extend.
(3) Delivering an orchestration solution on top of an application server avoids re-inventing the wheel, by leveraging the run-time facilities that are already in place (similar to databases using facilities of the underlying file systems rather than inventing their own). It also allows applications to be deployed and administered within infrastructure that is a known commodity in the operational infrastructure of most enterprises.
Dig Deeper on Business process modeling and design
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.