Firestore transactions vs sharded atomic writes for a hot document under concurrency
Goal: Keep commit latency predictable for a single Firestore document targeted by many concurrent clients while preserving application invariants. Firestore transactions use optimistic concurrency control and retry aborted commits with backoff, so tail latency appears only under contention. Atomic field transforms and sharded writes avoid read-modify-write c