Selected the existing managed Postgres instance as the place job rows survive an API redeploy, and kept the cache out of that role. Configuration followed the repo's existing database resources. Vendor docs were not opened, and no connection to the hosted instance was made. Schema and locking were proven only on a local cluster.
- What worked
- The existing database configuration was a clear place to pin durable queue rows that an API redeploy does not replace.
