A senior engineer notices two proposed services that will need to call each other constantly for every transaction. What does this usually indicate?
Select an answer to reveal the explanation.
Short Explanation
Constant chatter between two services is usually a sign they were never really two services. You've split logic that actually belongs in one cohesive service, so the boundary needs a dependency-analysis rethink.
Full Explanation
The correct option is the one saying the boundary was drawn without adequate dependency analysis, splitting logic that actually belongs in one cohesive service. Heavy cross-service calling is a classic symptom that the boundary cut through a dependency that should have kept the logic together, which is exactly what capability and dependency analysis is meant to catch. The option saying the two services were correctly separated and simply need a faster network is incorrect because faster networking treats a symptom, not the underlying boundary problem. The option saying the generative tool produced incorrect Java for one of the services is incorrect because chattiness is a structural issue, not evidence of a code generation error. The option saying the two services should be merged with every other service in the application is incorrect because the fix is to correct the specific boundary at fault, not to collapse the whole application into one service. For the exam, read excessive inter-service calls as a boundary-analysis failure.