Service A is an entity service that provides a set of generic and reusable service capabilities. In order to carry out the functionality of any one of its service capabilities, Service A is required to compose Service B (1) and Service C (2) and Service A is required to access Database A (3), Database B (4), and Database C (5). These three databases are shared by other applications within the IT enterprise. All of service capabilities provided by Service A are synchronous, which means that for each request a service consumer makes. Service A is required to issue a response message after all of the processing has completed. Depending on the nature of the service consumer request, Service A may be required to hold data it receives in memory until its underlying processing completes. This includes data it may receive from either Service A or Service B or from any of the three shared databases. Service A is one of many entity services that reside in a highly normalized service inventory. Because Service A provides agnostic logic, it is heavily reused and is currently part of many service compositions.
You are told that Service A has recently become unstable and unreliable and several of the service consumers that access it have had to raise runtime exceptions due to these problems. What steps can be taken to solve these problems without compromising the normalization of the service inventory?
Not sure if replicating data is the best move here.
BA
Barrie12 months ago
I think option B sounds like a solid plan.
BO
Bong1 year ago
Surprised that it’s so unstable with all those dependencies.
MA
Mattie1 year ago
Totally agree, it needs more autonomy!
MA
Marguerita1 year ago
Service A relies too much on external resources.
GE
Genevive1 year ago
Okay, let me think this through. I know STIR futures are more flexible than FRAs, so I'm leaning towards B. But I want to double-check the other options just to be sure.
VE
Veronica1 year ago
I'm pretty confident I know the answer to this one. Promises are asynchronous, so the 'Success' message will be logged after the 'End' message, even though the promise is resolved immediately.
LY
Lynelle1 year ago
I might be mixing things up, but didn't we cover that kickbacks aren't related to bidding equality?
EL
Elliot1 year ago
Okay, I think I've got this. The Commit Point setting determines when the cycle count data is committed to the inventory records. Since the client is using an external application as the source, we'll want to set this to "A number" to ensure the import process completes successfully and the data is properly recorded.
ER
Erasmo1 year ago
Honestly, I'm confused. I feel like service registries were more about management than types of logic.
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login