Amazon SQS temporary queues

Temporary Queue Client Now Available for Amazon SQS

Temporary queues help you save development time and deployment costs when using common message patterns such as request-response. You can use the Temporary Queue Client to create high-throughput, cost-effective, application-managed temporary queues.

How it works

The client maps multiple temporary queues onto a single Amazon SQS queue automatically, allowing your application to make fewer API calls and achieve higher throughput. When a temporary queue is no longer in use, the client cleans up the temporary queue automatically.

PS: So it needs one SQS to connect those Virtual ones

Benefits

They serve as lightweight communication channels for specific threads or processes.
They can be created and deleted without incurring additional cost.
They are API-compatible with static (normal) Amazon SQS queues. This means that existing code that sends and receives messages can send messages to and receive messages from virtual queues.

Virtual queues

Virtual queues are local data structures that the Temporary Queue Client creates

Creating a virtual queue creates only temporary data structures for consumers to receive messages in. Because a virtual queue makes no API calls to Amazon SQS, virtual queues incur no cost.
TPS quotas apply to all virtual queues across a single host queue. For more information, see Quotas related to messages. (Limitations)

When a producer calls the SendMessage or SendMessageBatch API action on a virtual queue URL, the Temporary Queue Client does the following:

Extracts the virtual queue name.
Attaches the virtual queue name as an additional message attribute.
Sends the message to the host queue.

While the producer sends messages, a background thread polls the host queue and sends received messages to virtual queues according to the corresponding message attributes.

While the consumer calls the ReceiveMessage API action on a virtual queue URL, the Temporary Queue Client blocks the call locally until the background thread sends a message into the virtual queue. (This process is similar to message prefetching in the Buffered Asynchronous Client: a single API action can provide messages to up to 10 virtual queues.) Deleting a virtual queue removes any client-side resources without calling Amazon SQS itself.

Request-response messaging pattern (virtual queues)

The most common use case for temporary queues is the request-response messaging pattern, where a requester creates a temporary queue for receiving each response message. To avoid creating an Amazon SQS queue for each response message, the Temporary Queue Client lets you create and delete multiple temporary queues without making any Amazon SQS API calls

The following diagram shows a common configuration using this pattern.