This presentation explores the evolving database needs of a rapidly growing startup. We follow a fictional company's journey from a very small team to a company with large user base facing regulatory obligations with a single PostgreSQL database. Discover how database access, migrations, and backups requirements change unexpectedly as customer expectations and data volume increase.
Practical insights for engineers and product owners to ensure long-term success.
Key takeaways - External-facing applications: No migration access or responsibilities. - Long-running (multiple days) migrations: Acceptable, no user or feature delivery impact. - Read-only replica offloading: Multiple database connections in the application. - PostgreSQL connection scaling: Connection pooler for primary instance. - Replication and backups: Complementary, as delayed replicas can help in some cases