PostgreSQL is the system of record for the operational PWAs we run. The screens and the API change. The figures for a harvest, a budget, or an invoice stay here.
Where it shows up
- Mountain Ridge Wines: pooling, vintage, harvest, budgeting, and invoicing share one database, so the close is not a merge of spreadsheets.
- The hosted service: the database runs with the app, on the managed server, with backups as part of the retainer.
- A boundary with SAP: on consulting work the ERP stays the client’s system. On a PWA we build, PostgreSQL is ours to run.
Why PostgreSQL
- Transactions, so a half-saved invoice is not a state the business can reach
- One database the FastAPI service and the SvelteKit app can both rely on
- Straightforward to operate under Docker, next to the rest of the stack