Citizen permit-status pages currently call the intake API, which calls payments, which calls inspections, and any hop timeout shows unknown during peak filing days. Which event-driven modernization should architects recommend?
Select an answer to reveal the explanation.
Short Explanation
Asking five offices in a chain whether a permit is ready is a game of telephone. Let each office post events and keep a status board the website can read. One timeout in the chain shouldn't blank the whole page.
Full Explanation
Synchronous multi-hop queries couple availability and latency across permitting, payments, and inspections. An event-driven design publishes domain events and maintains a status projection that consumers update independently so the citizen path reads a local view instead of traversing live dependencies. Additional HTTP hops, browser-to-database SQL, and a single in-memory cache without events preserve the reliability problem.