A payments notifier must publish events so billing and auditing can…

Question

A payments notifier must publish events so billing and auditing can consume them independently without the notifier knowing every subscriber. Which pattern best fits?

Accepted Answer

Publish events to Amazon SNS or Amazon EventBridge (optionally with SQS subscribers) so billing and auditing subscribe independently. — Pub/sub is the city PA system—payments announce once, and billing plus auditing plug in their own radios. Point-to-point SSH or one hard-coded URL ties the announcer to every listener by name.

Answer

Have the notifier call each billing and auditing database synchronously over SSH.

Answer

Hard-code HTTP posts from the notifier to a single fixed billing URL and skip auditing.

Answer

Store payment events only in an EC2 instance’s memory until an operator copies them by hand.

A payments notifier must publish events so billing and auditing can consume them independently without the notifier knowing every subscriber. Which pattern best fits?

Short Explanation

Full Explanation