A utility AMI platform emits one meter event that must trigger analytics, alerting, and archival compute paths without blocking the producer. Which messaging pattern best enables elastic fan-out?
Select an answer to reveal the explanation.
Short Explanation
One meter tick, many listeners—that’s pub/sub fan-out, not a single worker doing everything in line. SNS (or similar) fans the event so analytics, alerts, and archives each scale on their own. One sync loop, a global lock, or hourly FTP polling bottlenecks the utility stream.
Full Explanation
Publish/subscribe messaging allows a single event to fan out to multiple compute paths without blocking the producer, enabling each subscriber to scale elastically. For high-scale meter readings, SNS-style fan-out supports parallel analytics, alerting, and archival processing. Synchronous single-worker designs, global locks, and slow file polling prevent independent scale.