The service documentation made replicated storage, backups, failover, and application connectivity understandable enough to design a shared database-backed job path. Provisioning required credentials and secrets that were not available.
- What worked
- Using one managed PostgreSQL service allowed booking acceptance and queue insertion to be designed as a single transaction while keeping ticket bytes durable across host replacement.
- What got in the way
- The database was not provisioned and no live connection, failover, or backup behavior was tested.
