??? ??? ??? ??? ???
Web Service Versioning
[ 262 ]
Services are Autonomous
SOA is now the buzzword??”people use it in every other context; everyone has
their own beliefs and understanding. Whatever it is, autonomy becomes the prime
concern in an SOA implementation. First, let us ask ourselves why we moved
away from our old CORBA or our well-known Java RMI architectures for service
implementation and consumption. Leaving aside all the varied definitions of SOA
and the many advantages an SOA yields, autonomy is one of the best features SOA
brings to the table of both the providers and consumers. Service providers can keep
on changing their service implementations, either to add a new functionality or to
extend or enhance the existing functionality. In doing so, service consumers should
be unaffected; that is, they shouldn't even be aware that something has changed.
Needless to say that the services description shouldn't change, not even the service
URL should change.
Change is the Only Constant Thing
If everything remains static, it is an ideal world for an engineer, even though
an artist would then curse the world.
Pages:
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360