3 posts filed under transactions.
The MongrelDB PHP client stages multi-row writes locally, commits them as one atomic HTTP batch, and dedupes retries with storage-layer idempotency keys, so a timed-out request is safe to replay without building an outbox.
MongrelDB evaluates unique, foreign-key, and CHECK constraints atomically at transaction commit instead of per statement, which changes what a batch import can promise and what it has to fear.
MongrelDB binds idempotency keys into the commit log itself, so a retried write is safe across process crashes and restarts, not just across network drops.
