One of
the major causes is associated with the various structural compositions formed by services when
a solution is devised (discussed in Chapter 13, on service design). It was shown that properly
separating business concerns can alleviate this challenge. It was also shown that analysis and
design decomposition operations can reduce these service dependencies and contribute to a more
agile and distributed environment, one in which a modification to one entity will not affect the
associated assets.
But the service-oriented logical architecture faces different challenges. Here, the focus is on
a loosely coupled strategy that involves packaged technological solutions. The concern is no longer
about individual service associations and their structural formations. The major considerations are
dependencies and the agility of the overall service-oriented ecosystem. The principal questions
that should be addressed are related to the collaboration between the packaged service solutions,
their peers, and their enabling technologies. To better understand the logical architecture mission,
ask the following questions:
??? How is it possible to reduce the dependency between two or more packaged services?
??? How can the tight coupling between packaged services and third-party vendor products
be alleviated?
??? Can the implementation of architecture loose-coupling practices increase asset reusability?
??? What are the mechanisms for forming a loosely coupled deployed environment while not
degrading service performance?
The answers to these vital questions should be clearly addressed by considering the following
proposed logical architecture best practices.
Pages:
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605