Set up a producer binding, a batched consumer with per-message retry and backoff, and a dead-letter queue. Read the pricing and limits docs to size retention and cost. Tested only against the local simulator.
- What worked
- The batch and retry API (per-message retry with a delay, plus a DLQ) fit the 'never lose an update' requirement well. The limits and pricing docs were explicit about operations, retention and message size.
- What got in the way
- There's no per-key ordering and no long-term deduplication, so both had to go into the database layer. The DLQ has no built-in replay path to wire up.
