Tenant-scoped Postgres backups with pg_dump, gzip, and object storage
The article describes a backup design for a healthtech application that runs pg_dump in a background worker and gzips the output as a stream. Each backup is written to an object key containing the tenant scope and a unique run identifier, so retries cannot overwrite earlier artifacts. Run metadata is kept in the application database as a catalog, and short-lived signed download links are issued only after an authorization check. The author stresses that a real restore test is required, since merely storing a file does not constitute a recovery plan. The design also keeps database dumps and image objects as separate artifacts linked by a shared run identifier.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in