Breakout Session

on YouTube ↗47m

" summary

Heroku Postgres runs about a million databases on AWS and uses LXC containers to keep runtime images uniform while storing data separately, grows disks via EBS elasticity, archives WAL segments with Wally to S3 for point‑in‑time rebuilds, and builds hot‑standbys and forks from those backups. Monitoring and automated incident resolution restart resources or fail over followers, and the platform aims for immutable-ish servers so upgrades and large‑scale recovery work reliably.

AI-written summary · about

" chapters (11)

1. 0:00Start
2. 1:20What is Heroku?
3. 5:05Applications
4. 6:19heroku-postgresql heroku-redis
5. 14:30Automated incident resolution
6. 15:47Stuff happens constantly
7. 16:29Circuit Breakers
8. 20:12Immutable-ish Infrastructure
9. 22:05Durability and Availability
10. 28:41complicated project
11. 29:33composable services

" related talks

• 22mLessons from Automatic Incident Resolution for a Million DatabasesGreg Burek · SREcon16 Europe
• 46mBig databases, many servers, data center or cloud - it's all here!Flavio Gurgel · Devoxx France 2021
• 35mContainerizing PostgreSQL and Making it Cloud Native ReadyJeff McCormick · CloudNativeDay 2016
• 36mAutomated Performance Testing of PostgresGreg Burek · PostgresOpen 2014
• 19mPostgreSQL at AmazonJim Mlodgenski · Postgres Conference Orlando 2025
• 51mIdentity at Scale; How Okta uses PostgresNorberto Leite · PostgreSQL Conference Europe 2024
• 43mJust Use Postgres.Rhys Elsmore · PyCon Australia 2015
• 11mGiving your Heroku App highly-available PostgreSQLJake Varghese · RailsConf 2018