Amazon SQS

“The communication is over a shared database and SQS queues.”

“you're dealing with the real SQS, S3, etc, and if you have integration problems there, they're actually real things you need to fix for it to work in prod”

“when you hook them up to SQS you don't let AWS fire up like 2000 lambdas”

“our costs went from $6K/month (on savings plans, evemn) of ec2 to ~$400/month in lambda, sqs, and elasticache/redis”

“we have built a simple event system in top of lambda functions, sqs, s3, eventbridge etc”

“We have parts of the system connected to SQS for processing events”

“we used AWS-specific managed services like Lambda, Dynamo, and SNS/SQS”

“we're inconsistant in whether we use SNS vs. SQS”

“there are plugins for running the lambdas locally as well as for dynamodb, sqs, ses and eventbridge.”

“nobody ever "just wanted" an SQS queue.”

“A colleague would argue for what felt like hours against SQS because it was "random" ordering”

“These are the services we used.”

“Before we moved to NATs we had the added bonus that using SQS meant that there was no possible link”

“Usually, our graphql-server puts something to an SQS queue, and the lambdas pick it up.”

“we are already using SQS for a similar system that's currently in production.”

“We have an existing production system that uses a combination of SQS, DynamoDB, and Postgres, and EC2s”

“we use SQS to listen for S3 events and would love to switch to AMQ”

“We moved to Amazon SQS for now, but I imagine we'll move to something like Disque in the future.”

“Images are hosted on Amazon S3, we also queue uploads to S3 with SQS.”

“have been using more and more ACTUAL AWS services (SQS, DynamoDB, Redshift)”

“SQS queues are used to send and receive messages between our web portal and analyzers.”