When a boil-water advisory is declared, multiple municipal systems…

Question

When a boil-water advisory is declared, multiple municipal systems (SMS gateway, web banner service, utility IVR, and partner APIs) must be notified without each system calling the others directly. Which integration pattern best provides reliable fan-out?

Accepted Answer

Publish the event once to Amazon SNS and let subscribed systems (email, SQS, Lambda, HTTP, etc.) receive the fan-out independently. — SNS is the city loudspeaker: one boil-water shout, many departments hear it on their own channel. Hand-SSH and shared-spreadsheet phone trees couple everyone into one fragile knot.

Answer

Have the water-quality app open SSH sessions into every subscriber host and patch config files by hand.

Answer

Store the advisory only in a spreadsheet on a shared drive and require each team to poll it every hour.

Answer

Embed hard-coded IP lists of every consumer inside the water-quality monolith and restart it for each new subscriber.

When a boil-water advisory is declared, multiple municipal systems (SMS gateway, web banner service, utility IVR, and partner APIs) must be notified without each system calling the others directly. Which integration pattern best provides reliable fan-out?

Short Explanation

Full Explanation