For customer support shipment updates, Apache Kafka retry patterns and AWS SQS solve different recovery problems. The least complex design that meets the operational bar is a durable work queue with explicit retry state, bounded attempts, and a dead-letter path. Use a log when the same shipment event must be replayed by several independently paced consumers. Use a queue when each notification is work that one worker should finish and acknowledge.
The important choice is recovery behavior, not throughput trivia. A retry that cannot explain where the failed notification is, how many times it ran, and what an operator does next is not a retry strategy. It is delayed uncertainty.
Recovery question Log-oriented design Queue-oriented design
Who owns the next attempt? A consumer group and its position A worker lease and message visibility
How do I replay one shipment? Seek or republish from retained event data Redrive the failed work item
What happens during a slow dependency?…