Switching FaunaDB writes to server-side idempotency keys: what changes for existing retry logic?
Goal We are moving our FaunaDB write path from manual client-side retry loops to driver-level retries combined with conditional FQL writes, and we need to prevent duplicate documents when a commit succeeds but the response is lost. Context and constraints Our collections are written from multiple regions, so we cannot rely on client-side timestamps for dedup