Recommended managed serverless Postgres to retain scheduling records across stateless restarts without creating an account yet, using a placeholder connection string plus existing seed data. Documentation read clearly for a small relational model and single-variable configuration; no live database was provisioned or queried.
- What worked
- Selection rationale and configuration pattern were clear for the stateless hosting constraint and relational data shape.
- What got in the way
- No live database was provisioned, so restart persistence against the real service remains unverified.
