![]() Here are several important terms to understand before you start working with Amazon SQS: To dig deeper, check out the basic Amazon SQS architecture in the official documentation. This is a very simplified description of how message queueing works in SQS. Unlike the conversation, queued messages need to be deleted after processing to avoid their duplication. FIFO (first-in-first-out) model is used to process messages only once and in a strict order. Your app should be able to handle messages arriving more than once and out of order. This is the default type, which supports at-least-once message delivery. With Amazon SQS, messages can be processed in two ways: ![]() As soon as the consumer is available, the message is delivered and the consumer processes it (reads, forwards to another subscriber, etc.) In this case, the producer sends a message and if the consumer is not available at the moment, this message will “wait” on an intermediary server. For direct communication (like a call) both participants must be online and available.Īsynchronous communication is similar to messaging through a platform or even SMS. There always should be at least two participants: the producer (the one who sends the message) and the consumer (the one who receives it). If you are new to queueing, imagine this process as a communication between two subscribers on a mobile network. How does Amazon SQS work?Īmazon Simple Queue Service (SQS) is a message queuing service that enables you to manage asynchronous communication between applications or microservices. We will go over its basic functionality, main use cases, pricing, and common questions about this system and its integrations. If you are considering Amazon SQS for improving your app architecture and need to quickly understand its basics and decide if it’s a fit for your project – you are in the right place. When dealing with cloud-based infrastructure, it’s hard to pass by Amazon AWS.
0 Comments
Leave a Reply. |