A single case-closed event must feed both a searchable archive queu…

Question

A single case-closed event must feed both a searchable archive queue and a metrics queue, and each consumer must fail and scale on its own. Which pattern should the developer implement?

Accepted Answer

Publish the event to Amazon SNS and subscribe a separate Amazon SQS queue for archive and another for metrics — One megaphone, two mailboxes. SNS fans the same case-closed notice out to separate SQS queues so archive and metrics each scale and fail without taking the other down. One shared queue or a chained Lambda couples their fates; S3 list-polling is the wrong delivery bus.

Answer

Have one Lambda call both queues in sequence inside the same try/catch so either both succeed or both roll back

Answer

Write the event once to an S3 object and have both queues poll that object with ListObjects

Answer

Put both consumers behind one shared SQS queue and use message attributes to decide who processes it

A single case-closed event must feed both a searchable archive queue and a metrics queue, and each consumer must fail and scale on its own. Which pattern should the developer implement?

Short Explanation

Full Explanation