Multiple municipal apps publish inspection.completed events; a sing…

Question

Multiple municipal apps publish inspection.completed events; a single analytics consumer should not be wired into each publisher's code. Which EventBridge approach keeps publishers decoupled?

Accepted Answer

Use a custom EventBridge event bus and rules so publishers put events on the bus and consumers subscribe independently. — Put inspection.completed on a shared bulletin board — a custom EventBridge bus — instead of teaching every app the analytics team's phone number. Publishers post; rules deliver. Nobody rewires when a new consumer shows up.

Answer

Hard-code the analytics Lambda ARN inside every publisher and invoke it synchronously.

Answer

Give each publisher its own copy of the analytics code to run inline.

Answer

Require publishers to write directly to the analytics team's DynamoDB table.

Multiple municipal apps publish inspection.completed events; a single analytics consumer should not be wired into each publisher's code. Which EventBridge approach keeps publishers decoupled?

Short Explanation

Full Explanation