If the notice service fails, city payments should keep working, so teams avoid hard synchronous coupling everywhere. Which design goal are they pursuing?
Select an answer to reveal the explanation.
Short Explanation
Loose coupling is seatbelts between departments—when notices stall, payments can still take the money. Hard synchronous chains turn one hiccup into a citywide outage. Keep the blast radius small and citizens keep moving.
Full Explanation
Loosely coupled architectures reduce hard runtime dependencies so consumers are not forced into lock-step failure with every producer. Avoiding ubiquitous synchronous coupling preserves availability of critical paths such as payments when ancillary services like notices degrade. Host affinity and intentional tight coupling work against that resilience goal.