Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.

3recommend
2warn against
Dec 1, 2025first mention
Aug 20, 2026latest mention
Nov 25 – Oct 26
Used forjob queuemessage queuebackend stack

Why people recommend it

“We moved to SQS because it was one less thing we needed to spend time on.”

“it's always better to use something like SQS, Redis queues, etc.”

former CTOswitched from PostgreSQL LISTEN/NOTIFYon “Postgres LISTEN/NOTIFY actually scales”
Show 1 more

Caveats and dissent

“Amazon SQS has similar dynamics, and its reputation is far from stellar.”

“I feel this has made the world a (very slightly!) worse place”

Often compared with

Who recommends it in their own words

All comments 6

“We moved to SQS because it was one less thing we needed to spend time on.”

“it's always better to use something like SQS, Redis queues, etc.”

former CTOswitched from PostgreSQL LISTEN/NOTIFYon “Postgres LISTEN/NOTIFY actually scales”

“Amazon SQS has similar dynamics, and its reputation is far from stellar.”

“I feel this has made the world a (very slightly!) worse place”

“Stack includes Golang, Neo4j, AWS (Lambda, SQS, S3, DynamoDB)”

Threads where it came up

Data: amazon-sqs.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.

Keyboard shortcuts
j / kNext / previous item
o or EnterOpen selected item
/Search
g hHome
g tTop
g rRising
g cCategories
tToggle dark mode
?This help