Amazon Simple Queue Service (SQS) Reviews

Amazon Simple Queue Service helps me build scalable, loosely coupled data pipelines by enabling services to communicate asynchronously. It delivers messages efficiently even during traffic spikes, which is the thing I like most. It also simplifies workload distribution between producers and consumers, especially for ETL and event-driven use cases. Overall, it supports high-throughput messaging workloads without requiring infrastructure management.

I don’t have any major dislikes about Amazon Simple Queue Service (SQS).

It majorly solves the problem of asynchronous communication between components in data pipelines. It also addresses issues like system failures during traffic spikes by buffering incoming messages and processing them gradually, which has benefited me a lot.

Honestly, what I appreciate most about AWS SQS is how easy it is to get started and scale up. No need to mess with servers or manage any infrastructure. We rolled it out using the Serverless Framework, and the setup just clicked. Everything we needed was ready to go, no hassle.

The integrations are a huge plus, especially the way SQS hooks into AWS Lambda to trigger events. I like that the AWS Console keeps things simple. It’s easy to keep an eye on your queues, send test messages, and set up dead-letter queues. You don’t need to spend hours figuring it out. The UI is pretty straightforward.

I use Amazon Simple Queue Service (SQS) for its reliability and the way it prevents tight coupling between services, which is fantastic for handling traffic spikes or downstream failures. I find its simplicity and reliability really valuable. I like that it's easy to integrate into distributed architectures and it scales automatically without the need for infrastructure management. It's a very reliable and fully managed message queue with excellent scalability and minimal operational overhead.

Yeah, message debugging and tracing across distributed systems can sometimes be difficult. FIFO queues have throughput limitations compared to standard queues. That can be improved.

Amazon SQS solves multiple problems for me: preventing tight coupling between services, enhancing resilience during traffic spikes, easy integration into distributed architectures, and automatic scaling without infrastructure management. It's a reliable and simple solution with minimal operational overhead.

Simple. Integrates great with Lambda. Compliant.

Sometimes hard to monitor. reply / dead lettet etc can be simpler

Connecting async lambda functions

It is quite easy to setup in AWS console. Also, there are so many tutorials available to integrate it. Since its aws , we get good support in community forum and customer service. Its highly scalable, so we need not to worry on number of messages we receive.

Nothing as such, sometimes it gets tricky to find the SQS on which we are working as aws console is little difficult to navigate

We are using it to process product infromation from 1 system to another.

The pricing is the best part about AWS Cloud Storage.

We have a lot of options to store the data as per the requirement and the frequency of use of the data.

We can store the data and get cheaper prices in Ultra Warm storage for the data that is infrequently accessed, and hence we don't have to pay higher prices.

The cost-effectiveness of AWS Cloud is the best feature

At times the data-transfer speed between on-prem/local can be a bit slow while uploading to EBS/EFS.

AWS is providing elastic storage and it is a helpful feature as I don't have to keep track of the storage metrics, cleanup and lifecycle management.

.I like the scalability which is almost infinite

Well, at this point I can't think about something I dislike at SQS

We are using it to create a push application for connection to i

It is really easy to integrate, simple to use, and pay as you use. It also provides a free number of requests, so I have also used it in my projects. It has easy integration with other AWS services. It provides ease of Implementation based on the wide variety of network methods it provides.

It doesn't have packages to integrate with j2ee applications, like integrating a messaging queue in the standalone.xml file of a JBoss server as a messaging bean. We have packages for Active Mq or Rabbit Mq but not sqs.

We used it in my company for event driven architecture of our microservices. Some microservices communicated using the sqs like the notification service, logging service. We also used it to manage our transactions as messages from sqs would trigger a lambda that would perform the ledger operations and wallet operations. It is highly reliable although it is important to configure it correctly which might require some hit and trial in start.

Aws cloud Service is very convenient to use as it gives great speed for accessing data online and it is very helpful for sharing data to others very smoothly than other platforms

It needs high speed internet connection to access data from AWS cloud so it is quite expensive and also after implementing the same required high maintenance cost so it should be minimised

AWS cloud storage solve our cloud storage issue which used for accessing data anywhere and anytime without any problem from long time which is very benefiting us.