Transit dispatch needs many independent listeners when a bus route detour is published, without the publisher knowing each listener. Which messaging approach should application code use?
Select an answer to reveal the explanation.
Short Explanation
Detours should go out like a radio bulletin — one publish, many radios tuned in. SNS pub/sub lets listeners subscribe without the dispatcher hard-coding each one. That keeps the publisher blissfully unaware of the crowd.
Full Explanation
Pub/sub via Amazon SNS decouples producers from the set of consumers: new subscribers attach without publisher code changes. Point-to-point TCP or hard-coded HTTPS URLs recreate tight coupling. A single SQS queue with one consumer is point-to-point, not one-to-many fanout (though SNS can fan out to multiple SQS queues). Application code should publish once to the topic.