The loosely coupled paradigm depends on a
352 Ch. 16 Service-Oriented Logical Architecture Principles
number of crucial design decisions that must be considered when delivering a service-oriented
logical architecture to the organization.
ASSET DECOUPLING. Traditionally, throughout the course of multiple software development
generations, practitioners have been separating responsibilities of organizational software entities
because of their bulky structures and their unwieldy logical composition. Rather than managing
large software formations, they have been favoring smaller units, which contribute to an agile
architecture that must swiftly react to business and technological trends. Evidently, this rule of
thumb also applies to the service-oriented paradigm as well: a very coarse-grained service should
be broken down into smaller entities??”that is, finer-grained services. This analysis activity both
enhances their reusability and alleviates service monitoring and control challenges.
But the logical architecture may employ service-oriented assets, such as legacy applications,
middleware and software platforms, and service groups that are not subject to decomposition
activities because they have been packaged for integration initiatives. So how do loose coupling
best practices apply in such an integrated environment? The answer to this vital architecture
question depends on how autonomous an organization??™s technological assets are.
Pages:
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606