A city permit office wants new applications to publish a message so scanners and citizen notifiers react on their own schedules without waiting on one shared call stack. Which integration approach best fits that loosely coupled design?
Select an answer to reveal the explanation.
Short Explanation
Think of the permit submit like a town-square bell—ring once, and whoever cares shows up when they can. Publishing an event lets scanners and notifiers react on their own clocks without tying everything into one brittle call chain. That loose coupling is the whole point of event-driven integration.
Full Explanation
Event-driven architecture decouples producers from consumers by publishing domain events that interested services process asynchronously. Scanners and notifiers can scale, fail, and retry independently without blocking permit submission. Synchronous chaining or a single nightly batch increases coupling and reduces failure isolation, which Cloud+ DevOps fundamentals contrast with event-based integration.