Giving your Heroku App highly-available PostgreSQL
summary
Explains how a Compose / IBM Cloud HA PostgreSQL setup uses etcd plus a Governor/Patroni-style coordinator with HA proxy and WAL streaming to keep leader/follower nodes synced, then walks through the exact migration: grab a Heroku PG backup, pg_restore into the IBM Cloud connection string (nonstandard port), remove the Heroku Postgres add‑on so DATABASE_URL can be reset, set DATABASE_URL to the new host, verify in console; data copy is online, the config‑var switch causes the only brief downtime.
AI-written summary · about
chapters (9)
- 0:00High-availability PostgreSQL intro
- 1:25IBM Cloud PostgreSQL HA
- 2:57Demo setup and backup
- 4:00Restore to IBM Cloud PostgreSQL
- 5:29Heroku config for new instance
- 7:02Migrate data and final checks
- 8:33Downtime and sync handling
- 9:38Elasticsearch integration
- 10:43Summary
related talks
47mBreakout Session
33mHerding Elephants
46mDeploying Maximum HA Architecture With Postgres
01h 00mWriting Portable PostgreSQL - backed network applications for the open cloud
47mPostgreSQL High Availability: The Considerations and the Candidates
53mBest practices of using a managed PostgreSQL in the cloud
55mHigh Availability with PostgreSQL and Pacemaker
50mThe Immortal Postgres Web
