Strategies for managing change
One of the key design principles behind SOA is that systems should be designed and built to accommodate future changes in response to ever-changing business requirements.
So far, we have looked at how to design and build the initial system, so that when change does occur, it can be isolated through the use of service contracts to particular parts of the overall system.
While allowing us to restrict the impact of change, it doesn't completely mitigate all the complexities, especially when you consider that the consumer and provider of a service may be in completely separate organizations.
Major and minor versions
When we upgrade the version of a service, for example, from version 1 to version 2, then from the consumer's ...
Get Oracle SOA Suite 11g R1 Developer's Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
