Messages can be sent and received at any scale between software components using Amazon SQS. As a Solutions Architect, author assisted numerous clients in utilizing message queues for asynchronous interactions, and it was one of the first AWS services he used. Actually, Amazon SQS has been widely accessible since July 2006 and has always operated on the same XML-based wire interface, which AWS refer to as the AWS Query protocol.
AWS pleased to report that all APIs on Amazon SQS can now use a JSON-based wire protocol. Many of the drawbacks of the Amazon Query protocol are circumvented via the AWS JSON protocol.
When sending and receiving SQS messages, AWS JSON can lower latency and client-side CPU consumption more effectively than the prior XML-based protocol. For instance, with the outdated AWS Query protocol, the response body size for a request that sends a straightforward “hello world” message is roughly 400 bytes. Using the new AWS JSON protocol, the content length of the identical SendMessage response is less than one-third of the old size.
Utilizing Amazon SQS with the New JSON-Based Protocol
The best aspect of this launch is this! You only need to update the AWS SDK to the most recent version in order to take advantage of the AWS JSON protocol. The SQS team took great effort when developing this new capability to ensure that using the new JSON-based wire interface requires no code modifications.
To compare the two wire protocols, for instance, Amazon used the AWS SDK for Java to run a benchmark. Comparable outcomes are anticipated from the other AWS SDKs. The JSON protocol for Amazon SQS lowers application client side CPU and memory use as well as end-to-end message processing latency by up to 23%, according to AWS performance measurements with a 5KB message payload. These figures may not match what you observe for your own applications because they depend on the actual implementation.
Accessibility and Cost
In every AWS Region where SQS is enabled, support for the new JSON protocol is now available with Amazon SQS. AWS JSON for SQS APIs is now supported by all widely accessible AWS SDKs. All you have to do to reap the rewards of this optimization is update the AWS SDK to the most recent version.
Pricing stays the same while utilizing the AWS JSON protocol
AWS oldest service is being improved upon and innovated around after over 17 years of being widely available. A few months ago, AWS increased the default quota for high throughput mode for FIFO queues, announced support for attribute-based access control (ABAC) using queue tags, and enabled server-side encryption using Amazon SQS-managed encryption keys (SSE-SQS) by default for newly created queues. In order to handle dead-letter queue (DLQ) redrive programmatically, Amazon SQS provided new APIs lately. It’s always day one at AWS!
When utilizing Amazon SQS, update the AWS SDK to optimize CPU and memory utilization and lower latency.
[…] may also access the model through code examples in the AWS SDKs and Command Line Interface (AWS CLI) by selecting View API request. An example of an AWS CLI […]