Idempotency part 1: at-least-once, unique constraints and an Idempotency-Key on PostgreSQL
Why every distributed system is at-least-once, three ways to make an operation idempotent, an Idempotency-Key implementation tested with 20 concurrent requests on PostgreSQL, a case study of duplicate bookings caused by a non-unique request_id, and why a distributed lock is no substitute for idempotency.