Menu

Same message, four fates: SQS, SNS, Kafka and Redis Pub/Sub when a worker crashes
📰

Same message, four fates: SQS, SNS, Kafka and Redis Pub/Sub when a worker crashes

DEV Community: redis·Aleksandr Argunov·about 10 hours ago
#oASYXUOZ
#devtoredis#devto#dev#group#charge
Long article (910 words) — no AI summary yet.
Reading 0:00
15s threshold

Every broker delivers when nothing breaks. So compare them on the crash.

SQS = a take-a-number ticket. SNS = a group text. Kafka = a tape recorder. Redis Pub/Sub = live radio.

The grid

Kafka here means ordinary consumer groups. Share groups get their own section below.

Case SQS SNS Kafka Redis Pub/Sub

Who gets it Competing workers; standard can duplicate Every matching subscription Each subscribed group; one owner per partition Matching subscribers connected now

A worker dies Undeleted message becomes visible after timeout Retryable delivery failures get retries Resumes from committed offsets No replay

It keeps failing DLQ with a redrive policy Subscription DLQ for failed delivery, if configured Your code decides Nothing to retry

It arrives twice Standard can; FIFO deduplicates sends within its window and scope Standard can; FIFO deduplicates publishes within its window and scope Uncommitted work can repeat No redelivery; overlapping subscriptions can duplicate

Nobody listening Retained up to 14…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.