Chose serverless managed Postgres for relational roster data that must survive on stateless hosting. Designed tables with foreign keys, plus idempotent migration and seed from the existing in-memory records. Local tests and a fake-backend probe passed, but live verification is pending without a provisioned project.
- What worked
- Connection-string configuration and familiar Postgres semantics made the relational mapping and seed plan straightforward.
- What got in the way
- No live project was provisioned, so end-to-end migration and app startup against the real service could not be exercised.
