I interned on the SQS team back in 2006 and subsequently joined the team full time for a few years including briefly managing it. I have some great memories of that time. Keeping things 'simple' while scaling as AWS grew was a great introduction to the industry.
Most consistently excellent AWS product: it's a simple thing that does a simple job with minimal hassle. I suspect it will save me the trouble of ever having to run messaging infrastructure again.
As a side note - For someone not totally an expert in AWS it’s sometimes difficult to choose between SQS, SNS, EventBridge and the list of other related technologies.
Even though I first created images for EC2 in 2008, I've still never used SQS. I have a lot of experience with Google PubSub and this blog post is making me wonder if I should try leveraging SQS in production. I'm sure it's very mature, but I'm curious about how it feels from a developer perspective with a heavy production load.
The last time I used SQS it was kinda expensive because I had to poll every minute or so it ate up the free tier. If I wanted to poll faster (like every 5 seconds) it was even more expensive. Maybe not the best use for my use case.