A city’s microservices team must ingest a brittle on-premises mainframe feed into modern permit services without letting mainframe outages stall the new apps. Which loosely coupled pattern best isolates the modern tier?
Select an answer to reveal the explanation.
Short Explanation
Treat the mainframe like a cranky neighbor—don’t let it bang on your front door. Drop its feed into an SQS buffer and let modern apps pick up work when they’re ready.
Full Explanation
An anti-corruption layer using Amazon SQS decouples brittle legacy producers from modern consumers: messages persist while the mainframe stalls, and services scale independently. Direct synchronous JDBC, unbuffered public NLB calls, and credential sprawl couple failure domains and amplify outages instead of isolating them.