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

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.

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.

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

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.