4 ms·
I feel like the create/delete queue semantics hint that a queue should be a long-lived thing that consumers are configured to connect to. When I saw suggestions
by stellar678 7y ago
I feel like the create/delete queue semantics hint that a queue should be a long-lived thing that consumers are configured to connect to. When I saw suggestions to have one queue per consumer and have that consumer create/delete the queue during its execution lifecycle, the idea of one-queue-per-consumer started making more sense to me.
- staticassertion 7y agoI think the word "Consumer" here is "Consumer Group". For example, an AWS Lambda triggered from SQS will lead to thousands of executions, each lambda pulling a new message from SQS. But another consumer group, maybe a group of load balanced EC2 instances, will have a separate queue. In general, I don't know of cases where you want a single message duplicated across a variable number of consumer groups - services are not ephemeral things, even if their underlying processes are. You don't build a service, deploy it, and then tear it down the next day and throw away the code.