#423 · bluetape4k-aws · 1.0.0 · SQS payload lifecycle

Follow the payload until acknowledgement and cleanup finish.

Compare inline and S3-offloaded payloads through a module-local signed pointer, bounded restore, handler completion, SQS delete, marker creation, payload cleanup, and an opaque retry handle.

Choose a payload lifecycle

Inline, offload, and failure path × 9

Payload lifecycle sequence

Step 0 / 8

Lifecycle progress1 · Choose inline or offload

Scroll horizontally to inspect the full payload lifecycle →

Producersize gate + idempotency

Amazon S3payload + cleanup marker

Amazon SQSinline body or signed pointer

Extended consumerbounded restore + acknowledgement

Application handlerbusiness completion

UTF-8 payload bytes ≤ offloadThresholdBytes?

1 · Choose inline or offloadwaiting
Put payload before queue send

2 · Store the large payloadwaiting
SqsOperations.send(body)

3 · Send body or signed pointerwaiting
receive → pointer verify → bounded S3 read

4 · Validate and restorewaiting
Materialized payload

5 · Run the application handlerwaiting
Handler success

6 · Complete business workwaiting
sqsOperations.delete(queueUrl, receiptHandle)

7 · Delete the SQS receiptwaiting
put-if-absent marker + constant-time metadata check

8 · Create or verify the markerwaiting
delete(payloadKey)

9 · Delete or retry payload cleanupwaiting

1 · Choose inline or offload

waiting

UTF-8 payload bytes ≤ offloadThresholdBytes?

What happens

Guardrail

What follows

Visible signal

Adapter-owned

No automatic bucket, IAM, lifecycle, or AWS Java Extended Client interoperability

│ ack before cleanup │

Caller-owned

This offline explorer models bluetape4k-aws ordering. The pointer is local to this module and is not interoperable with the AWS Java Extended Client or a legacy @SqsListener. The application must provision S3, IAM, encryption, retention, lifecycle, rollout, rollback, retries, and orphan cleanup.

Use the step buttons or Left/Right/Home/End. Play advances this offline explanation only.