The
SOA Gateway enables your core software assets, including data and business logic, to be exposed as standards based services that can be used from multiple client technologies. Once a service has been deployed and is in use from one or more systems, there are reasons why it may change:
- In order to improve the functionality available to the users.
- In order to improve the business process with which it was associated
- Users asked for something and didn't like what they got
- ...and so on
The problem with this is when a service is deployed, how does one control change to this service ? Many organizations implement multiple versions of a similar service when a well designed single service will do. The
SOA Gateway is being modified to provide the facility to ensure that the lifecycle of a service can be controlled such that a single service and its clients may be enchanced in a controlled fashion as described
here.
This is still a work in progress so we're always interested in ideas or feedback to the direction we plan to take.
Best regards,
John
No comments:
Post a Comment