So far so good, now the final question??”for scenarios that we have seen above,
should we create a new version of the existing service or should we define a new
service itself by not disturbing the existing one?
Rather let us restate the above points in this manner??”in SOA, services shouldn't
mutate from version to version. This will safeguard any existing consumers.
However, new services can be introduced which is not too complicated because
new services will have their own separate endpoints. Moreover, irrespective of
whether the consumers are new or existing, they will use the new endpoint to avail
the new service. At the same time services can also be enhanced or upgraded. An
enhancement can involve increasing the QOS features of the service or bringing in
Chapter 14
[ 265 ]
new implementation technologies behind the scenes, keeping the service interface
untouched. When you upgrade a service, you can now decide what to do with the
"old version" of the same service. I purposely used the words "old version" this time
because versioning of services makes sense in the context of enhancing or upgrading
services only, not in the context of introducing new services.
Pages:
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365