All Q's answered for SQS
January 31, 2022
All Q's answered for SQS
Score 7 out of 10
Vetted Review
Verified User
Overall Satisfaction with Amazon Simple Queue Service (SQS)
Our Application was integrated with third-party app, to fetch updated data from third-party app without keeping users to wait, we used SQS to bring data out of sync from users call. As user's request is sent to SQS queue and data is updated in our system.
- Dead letter queue for failed messages
- Queue management
- Message delivery to listener
- More frequest polling will be expensive
- No detailed monitoring of queues, just current data and regular monitoring is present
- No way to fetch messages back from the queue
- Queue management by removing individual ActiveMQ Queue results in less management of individual servers
- In a multi server system , sync between all servers is achieved with reduced Development efforts for handling sync
- Direct impact on time taken to serve messages results in fast and optimised performance
Simple and quick implementation makes it a first go to service when not familiar with queue management. Handling of Dead messages in queue is helpful, as over time these messages stack up causing lots of unnecessary processing at listener end. Retry mechanism for failed messages in systrem is a fine functionality as failed messages need to be handled for a fail safe system Delay implemeted to send message for polling makes it better to build a system which processes heavy data at listener end so to manage messages better before polling
Do you think Amazon Simple Queue Service (SQS) delivers good value for the price?
Yes
Are you happy with Amazon Simple Queue Service (SQS)'s feature set?
Yes
Did Amazon Simple Queue Service (SQS) live up to sales and marketing promises?
Yes
Did implementation of Amazon Simple Queue Service (SQS) go as expected?
Yes
Would you buy Amazon Simple Queue Service (SQS) again?
Yes