At-least-once delivery: how do you avoid duplicate side effects in a consumer?

Answer

Assume duplicates and make the handler idempotent. Common patterns: store a processed message ID with a unique constraint, use upserts, and keep changes + dedup in one transaction (inbox/dedup table).