These design examinations will make it possible to coherently
relate a service to its business and technological surroundings and to rationalize its links to
consumers. Thus, design relationship practices call for articulating these service associations to
the architecture and construction teams by providing them with lucid logical design blueprints.
The Law of Demeter (LoD),1 a software design guideline that was proposed in 1987 at
Northeastern University in Boston, introduced a different view of software entity associations.
This practice was related to the object-oriented paradigm. It suggested that an object should have
limited knowledge of other objects??™ internal structures or attributes for the purpose of software
decoupling, reuse,2 and component dependency reduction. The LoD also advocated that entities
should ???talk??? to their ???friends??? and avoid communicating with ???strangers.???3
Indeed, the traditional LoD concept and other contemporary service-oriented architecture
(SOA) design best practices advocate that a service should be an autonomous entity when it comes
to its internal affairs. This assertion also pertains to the method by which a service communicates
with its environment??”peer services and consumers. In addition, aspects such as message propagation
methods, service visibility, and software isolation are the main concerns of this chapter.
Consider the following six major concepts that contribute to the service-oriented logical design
relationship strategy:
1.
Pages:
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406