I have a service composition with three services. Service A retrieves a list of country codes from a database and keeps this data in memory while interacting with Service B and Service C. However, because Service A is concurrently invoked many times, and because each instance of Service A loads its own copy of the country code data into memory, the demands on the overall infrastructure become too high and performance and reliability are negatively affected. Which service-orientation principle can be applied to help solve this problem? Select the correct answer.
Suggested Answer: D
Get Premium S90.03 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
9 comments · newest first
LI
Lizbeth
12 months ago
Service Reusability could also play a role, right?
BE
Belen
12 months ago
Wait, are we sure statelessness is the best approach here?
RA
Raul
1 year ago
But wouldn't that mean losing some performance benefits?
CL
Clay
1 year ago
I agree, stateless services would definitely help reduce memory load.
CA
Cassi
1 year ago
Sounds like a classic case for Service Statelessness!
MA
Marsha
1 year ago
Okay, let's think this through. The key is reconfiguring the system for the new Planning Optimization master planning engine, so we need to focus on the firming time fence.
GR
Graciela
1 year ago
I think we might have practiced something like this, but I'm not entirely sure what transparency really entails in this context.
TW
Twanna
1 year ago
Composition sequencer sounds familiar, but I'm uncertain if it's a runtime role. Maybe I'll just go with what I know.
IV
Ivette
1 year ago
Ah, this is a good one. I know the importance of getting buy-in from senior leadership, but I also can't ignore industry best practices. I'll need to weigh all the options carefully.