Keep HTTP Calls Outside the Checkout Transaction
A slow shipping request should not hold stock locks. Commit a pending order and durable delivery intent, then recover the external step explicitly.
Rust database recovery
Start with the state your caller can observe. Check the stored result and choose a recovery path with a clear database and application boundary.
Two Webhook Deliveries Need One Database Claim
Two webhook handlers can both pass an existence check. Use a unique database claim, bind it to the payload, and commit it with the business change.
Use a Separate Database Identity for Migrations
Separate schema ownership from normal application access. Test that the runtime account can do its work and cannot change the tables or security policies.
Return HTTP Success After the Database Commit
Follow a checkout result through the commit and HTTP response. Handle rollback and a lost commit response as different outcomes.
A SQLite Import Can Block Normal Saves
Keep an interactive SQLite importer resumable and bounded. Commit batches with their progress and give foreground writes an explicit busy policy.
A Rejected PostgreSQL Import Row Needs a Recovery Path
Give failed import rows durable identities, bounded diagnostics, and a repair path. Make the batch's atomicity and replay behaviour explicit.