In
addition, an intermediary is capable of enriching transformed information and augmenting missing
data.
In very small service-oriented implementations, however, where a limited number of services
and consumers interact, an intermediary would be extremely ineffective. In fact placing
an intermediary entity between consumers and services in small scale and time-critical mission
deployment environment can result in performance degradation and unnecessary network bottlenecks.
Therefore, think about engaging intermediary products when the chief goal is to bridge
heterogeneous computing environments and to expand the design scope to foster loose coupling
best practices.
INTERMEDIARY ROLES AND RESPONSIBILITIES. The relationship that a consumer or a service
has with an intermediary depends on its specific role and responsibility. Let us now visit some
common industry intermediary categories to exemplify their proposed values to the serviceoriented
design relationship delivery. Thus, consider the following intermediary functionalities
that typically can be delivered by third-party vendor products, such as enterprise service buses
(ESBs), gateways and intermediaries, and even service life cycle management.
??? Message Transformer. An intermediary that is responsible for message transformation
typically provides three major types of message conversions: (1) protocol conversion
between two or more communication protocols, used by a variety of operating systems and
platforms, (2) transformation between different data formats, and (3) translation between
two or more security models.
Pages:
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436