sqs_extended_client 0.1.0 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f4fa6e3026a96530fc60de516f4817f5d2ff08f106f48fef058728e83aafa0b6
-  data.tar.gz: 192fcc74a733f1780e0d50fa6092ad29e462010128c897b8111f27135b675b87
+  metadata.gz: b1c58bcf0ebf9756ac0203bef44eed13755955402e15ccbce16699c54dc789ae
+  data.tar.gz: ca0a37de8e6b60546b1c3e117a7a8bd277d43f8076278822c1be2b743b13ae7b
 SHA512:
-  metadata.gz: adbb8b60ba77329fb74f8a52d69397ac41dff4263cb5a932bcca4f158041d766987480aad947a6b15ac91f2e8d6a2deeb660025030cea82fc70cfa6f19cf8e65
-  data.tar.gz: a5d05a27eee220902bec964d8645f1f77c4a9bdea6da9461b676451d5cb42618bd52549027f502dbb764e79aebb0425c106ef47d003d232ebc5ccd4203952a83
+  metadata.gz: 764412c79b2044152d198628021e7636df8193b08ad3d1d9f40cdf3e5fcced59f5615eea9bd03305ad574173bcf8ff4a958c1268c8eaef7afb4f68a64ad55ff6
+  data.tar.gz: e3816f9b9acc7f2a6cdfd679868f5d6330dd1862e3003477d635dd76f9c8ce2ccca31a5e5d1443f39bbdcec70d61ec8ddffc33ab5ef5ff1191b01de493528773

data/CHANGELOG.md

@@ -1,8 +1,25 @@
 # Changelog
 
-## [Unreleased]
+## [0.2.0] - 2026-09-18
+
+### Changed
+
+- `payload_size_threshold` now defaults to `1_048_576` rather than `262_144`. AWS raised the
+  maximum SQS message size from 256 KiB to 1 MiB in August 2025, so the old default sent
+  payloads to S3 that the queue accepts directly. Bodies between 256 KiB and 1 MiB now go
+  inline. Pass `payload_size_threshold: 262_144` to keep the previous behaviour, which is
+  also what the AWS Java and Python clients still default to.
+
+### Fixed
+
+- Corrected the 256 KB message size limit quoted throughout the README and the gem summary.
+- Documented that `SendMessageBatch` is capped at 1 MiB in total rather than per entry, so a
+  batch of bodies that are each under the threshold can still be rejected.
+
+## [0.1.0] - 2026-09-18
 
 ### Added
 
 - Initial release: `SqsExtendedClient::Client`, an `Aws::SQS::Client` wrapper that offloads
-  message bodies larger than 256 KB to S3 and restores them on receive.
+  large message bodies to S3 and restores them on receive, wire compatible with the AWS SQS
+  extended client libraries for Java and Python.

data/README.md

@@ -1,6 +1,6 @@
 # sqs_extended_client
 
-Send and receive Amazon SQS messages larger than the 256 KB limit by storing the body in S3
+Send and receive Amazon SQS messages larger than the 1 MiB limit by storing the body in S3
 and putting a small pointer on the queue instead. It is a wrapper around `Aws::SQS::Client`,
 so anything it does not need to touch is delegated straight through.
 
@@ -56,8 +56,11 @@ client.send_message_batch(
 )
 ```
 
-Remember that SQS sizes a batch by what actually goes on the queue. Offloaded entries are only
-a pointer each, so a batch of large payloads still fits comfortably under the 256 KB batch cap.
+Mind the batch cap: SQS limits a `SendMessageBatch` to 1 MiB **in total**, the same number as
+the per-message limit. The threshold here is per message, so ten 500 KiB bodies are each under
+it, none are offloaded, and the batch is rejected with `BatchRequestTooLong`. When you batch
+large payloads, set `payload_size_threshold` to roughly the batch cap divided by the number of
+entries so they offload to pointers first.
 
 ### Polling
 
@@ -115,7 +118,7 @@ client.change_message_visibility(
 | Option | Default | Meaning |
 | --- | --- | --- |
 | `bucket_name` | required | S3 bucket the payloads are written to. |
-| `payload_size_threshold` | `262_144` | Offload once body + attributes exceed this many bytes. |
+| `payload_size_threshold` | `1_048_576` | Offload once body + attributes exceed this many bytes. |
 | `always_through_s3` | `false` | Offload every message regardless of size. |
 | `cleanup_s3_payload` | `true` | Delete the S3 object when the message is deleted. |
 | `ignore_payload_not_found` | `false` | On a missing S3 object, delete the SQS message and skip it instead of raising. |
@@ -154,6 +157,12 @@ Only the operations that need it are overridden: `send_message`, `send_message_b
 
 ## Caveats
 
+- The default threshold follows the current SQS limit of 1 MiB, which AWS raised from 256 KiB
+  in August 2025. The AWS Java and Python extended clients still default to 262_144, so the
+  same payload may offload there and go inline here. That is a local cost decision, not a
+  compatibility one: both sides read whatever they are given. Set
+  `payload_size_threshold: 262_144` to match them, and do the same against an SQS-compatible
+  endpoint such as LocalStack or ElasticMQ that has not adopted the larger limit.
 - SQS allows 10 message attributes and the reserved one takes a slot, so an offloaded message
   may carry at most 9 of your own.
 - Nothing here expires S3 objects on its own. Set a lifecycle rule on the bucket so payloads

data/lib/sqs_extended_client/configuration.rb

@@ -2,8 +2,11 @@
 
 module SqsExtendedClient
   class Configuration
-    # SQS caps a message at 256 KiB; anything larger goes to S3.
-    DEFAULT_PAYLOAD_SIZE_THRESHOLD = 262_144
+    # SQS caps a message at 1 MiB (raised from 256 KiB in August 2025); anything
+    # larger goes to S3. Set payload_size_threshold to 262_144 to match the AWS
+    # Java and Python extended clients, which still default to the old limit, or
+    # when the endpoint is not the real SQS.
+    DEFAULT_PAYLOAD_SIZE_THRESHOLD = 1_048_576
 
     # SQS allows 10 message attributes and the reserved one takes a slot.
     MAX_ALLOWED_ATTRIBUTES = 9

data/lib/sqs_extended_client/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module SqsExtendedClient
-  VERSION = "0.1.0"
+  VERSION = "0.2.0"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: sqs_extended_client
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.2.0
 platform: ruby
 authors:
 - Ngoc Bui
@@ -85,6 +85,6 @@ requirements: []
 rubygems_version: 3.4.10
 signing_key:
 specification_version: 4
-summary: Send and receive SQS messages larger than 256 KB by offloading the payload
+summary: Send and receive SQS messages larger than 1 MiB by offloading the payload
   to S3.
 test_files: []