Amazon 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.

SQS will be helpful for usage in terms of creating a Async flow to your system with though high usage but not high importance data sent to SQS.Whereas in cases where we need to manage messages and auditing of them sent to SQS , also to monitor performance of system integrated with SQS , in such cases SQS would not be a preferred option.Best thing about SQS is that it is quite easy to implement and manage which makes it quick and hassle free.

SQS is one of AWS services we are using for many different projects.
It helps us to dissociate the components of our architectures and to create the best asynchronous processes possible

SQS can be used when you need to create an architecture with asynchronous operations and when you are building many microservices that need to exchange messages.
It is different from SNS which allows you to broadcast messages to various targets

Amazon SQS is being used by several teams internally for various functions. SQS works great in conjunction with Lambda and other AWS services to serve needs for both internal applications as well as customer facing applications.

If you are looking to build something that just requires a simple queue service (as the name implies) this is great for it. You might look elsewhere though if you get into more complicated needs. This is also very well suited if you are already using other services with AWS and intend to fully build whatever you are building in AWS. If you are looking for a mixed environment -- SQS is not for you.

We use Amazon Simple Queue Service (SQS) to manage even queues for several of our internal applications. We have an application that receives and processes jobs for ad placement on different advertising platforms. These jobs are relatively critical, and reliable processing is a must. Amazon Simple Queue Service (SQS) provides a serverless queue to handle these requests for us as well as a target that can be tracked to keep a job status as well as capture any errors executing the job.

While we use AmazonSimple Queue Service (SQS) in our serverless applications, it would be a great option to handle queue management for any internet-connect application. It provides the most benefit in situations where your application or service must maintain mission-critical queue of messages or jobs. If you're already using other AWS services you will find the greatest benefit.

SQS service is under use at the company level, to handle the different application-level requirements. We mostly use it to decouple different level of modules so that we can provide an efficient solution to the end user.

We needed an application where we could communicate between asynchronous modules, and we needed a reliable solution where we could upload data under the HIPPA compliance, and Amazon SQS is the best fit.

We use Amazon SQS to decouple and scale our micro-services. Some of our services are responsible for ingesting objects from external APIs. We then need to transform and store these objects. We use SQS to decouple the services responsible for ingestion and transformation. This allows us to easily scale either service tier; it also allows our developers to focus on just one responsibility. SQS is used only by the engineering team. It helps to improve developer velocity; our services have only one responsibility and are easy to reason about and test. It also helps us to inexpensively scale only some tiers in our system.

Amazon SQS is great for decoupling micro-services. Decoupling services can result in smaller services that are easier to understand and independently deployable, improving developer velocity. It is also easy to scale tiers independently. SQS is especially great if message order and exactly-once processing are not essential. If you have these requirements, you can still try FIFO queues, but their throughput is limited.

We used Amazon SQS primiarly as a service queue to perform asynchronous methods for Mandrill emails for customers. It was used by the Engineering team on behalf of the Marketing team.

If you are trying to handle a large messaging queue to your customer base, specifically with email marketing notifications in mass quantities, this is a great tool. If you’re doing more personality, one-off messaging then this is not the ideal service.