Large SQS and SNS messages in Kotlin: the extended client pattern without Java baggage
Every SQS queue and SNS topic has a message size limit. When a payload is larger, the usual answer is the claim check pattern: put the payload in S3, send a small pointer instead, and resolve the pointer on the receiving side. AWS ships this pattern as two Java libraries, amazon-sqs-java-extended-client-lib and amazon-sns-java-extended-client-lib , both built on…
SQS and SNS have limits on message size. When payloads exceed these limits, the claim check pattern is used. AWS provides this pattern as Java libraries, but these libraries do not work with Kotlin on AWS SDK for Kotlin. To address this, three libraries were created on Maven Central: s3overflow for storing payloads, sqsoverflow for offloading large messages in SQS, and snsoverflow for offloading large messages in SNS.
The post explains the limitations of the Java libraries, the process of porting them to Kotlin, and the benefits of using these ports.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
