A county microservices mesh for licensing still calls five downstream services synchronously on every citizen request, creating multi-hop latency and cascading timeouts under load. Which architecture pattern change best improves performance while preserving eventual consistency where allowed?
Select an answer to reveal the explanation.
Short Explanation
Think of five clerks who each wait for the next clerk before speaking to the citizen—painful. Put non-critical steps on a message bus so the front desk can answer while the back office catches up. Async messaging cuts that latency chain.
Full Explanation
Synchronous multi-service chains multiply latency and failure domains. Moving eligible steps to SNS, SQS, or EventBridge decouples producers and consumers, improving responsiveness for municipal portals that can tolerate eventual consistency for secondary workflows. Extra synchronous hops, single-AZ monoliths, and disabled timeouts do not remediate the performance pattern and often reduce reliability.