Question

A retail company publishes all order events to a single Amazon SNS topic. Three separate microservices subscribe via Amazon SQS queues: a fulfillment service that should only process events where orderType is 'physical', an email service that should only process events where orderType is 'digital', and an analytics service that must receive every event. Currently all three queues receive every message, forcing the fulfillment and email services to inspect and discard irrelevant messages, wasting compute. Which approach delivers only the relevant messages to each subscriber with the least custom code?

Accepted Answer

Apply SNS subscription filter policies to the fulfillment and email queue subscriptions based on the orderType message attribute, and leave the analytics subscription with no filter.

Answer

Create three separate SNS topics and modify the publisher to send each event to the correct topic based on orderType.

Answer

Enable SQS FIFO queues with message group IDs set to the orderType so each queue only receives its group.

Answer

Add an AWS Lambda function subscribed to the topic that inspects each message and forwards it to the appropriate SQS queue.