Idempotency & Exactly-Once (Why It Matters)

Because at-least-once can duplicate deliveries, consumers should be idempotent: reprocessing the same message doesn’t change the result (use keys, dedupe tables, or transactional outbox). Even with Kafka’s exactly-once features, end-to-end guarantees depend on the whole pipeline.