In this scenario, some
activities may occur in succession, while others will be launched randomly or at the same time.
TAGGING INTERMEDIARIES
And finally, before we move on to elaborating on the service-oriented relationship deliverables,
let us discuss the last missing piece in this puzzle. So what is actually tagging intermediaries?
Tagging means identifying the roles and responsibilities of an intermediary in a design relationship
diagram (discussed later in the Service-Oriented Logical Design Relationship Diagram section).
An intermediary is typically located between message exchange parties to augment their functionalities.
More specifically, from an implementation perspective, a consumer does not need to
know the physical location of its corresponding service, and visa versa. The intermediary entity
has the intelligence to map this addressing challenge. But such a mediating broker can do much
more for service and consumer collaboration.
250 Ch. 12 Service-Oriented Logical Design Relationship
The service-oriented intermediary role is a design necessity that should not be ignored.
It is obviously not a new concept. It has been used for years for achieving loose coupling
architecture effects and promoting software asset reuse. One of the most important purposes
of utilizing intermediaries is their capabilities to resolve interoperable challenges by performing
data transformation between incompatible data formats, and even protocol conversions.
Pages:
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435