How do you handle consistency between a database and file storage?

How do you handle consistency between a database and file storage?

A database update and an object upload are usually separate operations. A design must account for partial completion instead of assuming they succeed together.

Use explicit intermediate states

Create an artifact record as pending, upload to a controlled object key, verify the object, and then mark the record ready. These are example steps; the important point is that a pending record must not be presented as a finished download. Make finalization repeatable.

Reconcile partial failures

If upload succeeds but the database update fails, retain enough identity to retry or clean up the object. If a ready record points to a missing file, show a recoverable error and investigate rather than silently treating it as valid. Define deletion similarly, with a state and retry path for both sides. Test failures between each operation to identify orphaned objects and broken records before users encounter them.