Database Reference
In-Depth Information
In this case, the implementation of a new business process would be achieved by simply
recomposing existing service capabilities in the sequence and duration as per the new
functional context.
We will need some hypothetical area where this recomposition will be possible technic-
ally. There shouldn't be any problem, as the protocol, data, and interfaces stay homogen-
ous. Any programming language or platform will do if the result of the recomposi-
tion—the new service—follows the initially declared standards for the services.
The fact that a newly composed application is also the service is important, as this com-
position could potentially be part of an even bigger composition; therefore, all strict stand-
ards must be applied all the way. This idealistic picture is pretty close to the contemporary
SOA model. We have only one solid framework here that is used for business service
composition, and with this, we practically accomplish very little. All our compositions
would be just invocations of existing APIs' capabilities with values' assignments in
Search WWH ::
Custom Search