Question 5

Question

Service A has become increasingly difficult to maintain. Its core service logic has become bloated and
convoluted because it has been updated numerous times during which additional functionality was
added to interact with the database and the legacy system and to support interaction with Service
Consumers A and B (via the two service contracts) as well as interaction directly with Service
Consumer C .
https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/Arcitura__S90.09/page_27_img_1.jpg
What steps can be taken to solve these problems and to prevent them from happening again in the
future?

Accepted Answer

The Official Endpoint pattern can be applied to limit access to Service A to one of its two published
service contracts. The Service Loose Coupling principle can be applied so that Service Consumer C
does not negatively couple itself directly to the core service logic of Service A . B . The Service Facade
pattern can be applied to position a Facade component between the core service logic and the
implementation resources (the database and the legacy system) and to position a faade component
between the core service logic and the two service contracts. The Contract Centralization pattern can
be applied to limit access to Service A to one of its two published service contracts. The Service
Abstraction principle can be applied to hide the implementation details of Service A from service
consumers.

Premium Access Includes

FLASH OFFER

avail 10% DISCOUNT on YOUR PURCHASE