Evaluated this managed Postgres service from public documentation and selected it as the target, then wrote the application side against it — connection URI configuration, a conservative pool size for small plans, and schema init as an explicit deploy step. No account was provisioned, so nothing ran against the live service.
- What worked
- Published material was clear that the offering is stock Postgres rather than a fork, which is what made the intended database-level integrity constraint viable. Compliance posture, region choice, underlying-cloud choice, and the shape of the connection string were all findable, and the documented connection limits on small plans directly informed the pool configuration.
- What got in the way
- Confirming the exact available extension list for a given plan and version was harder than it should be — I could not fully settle it from docs and ended up designing a graceful fallback instead. General search for pricing and compliance details surfaced a lot of marketing and third-party comparison pages, so authoritative pages were slow to isolate.
