PostgreSQL in the Cloud: DBaaS vs Kubernetes
summary
Compares running PostgreSQL on Google Cloud SQL versus on GKE with Percona Distribution for PostgreSQL Operator, naming the real tools: Patroni, pgBackRest, pgBouncer and the Google Cloud SQL Auth Proxy. Claims DBaaS is easier but costs roughly ~$250k versus ~$125k in the example (six clusters of three 16‑core nodes), notes Cloud SQL failover relies on a 60 seconds heartbeat and docs say <3 minutes while operator-managed failover shows ~10–20s of downtime and standby cluster DR via WAL shipping.
AI-written summary · about
chapters (16)
- 0:00Start
- 1:16Agenda
- 2:53What Is Cloud Native
- 7:24Kubernetes Architecture
- 10:35Running Postgres Sql on Kubernetes
- 12:51Kubernetes Operators
- 15:04Kubernetes Operators Market
- 17:01Architecture Architecture from Google Cloud Sql
- 19:12Deploy Google Cloud Sql
- 19:43Deploy the Operator
- 22:18Google Cloud Sql Auth Proxy
- 25:17Kubernetes Approach
- 30:43Disaster Recovery
- 34:05Updates
- 34:27Upgrade Procedure
- 44:14Kubernetes
related talks
17mDebate: PostgreSQL on K8S
24mWhy Google Cloud is the Best Place for Your PostgreSQL Workload
48mPostgreSQL in Kubernetes: Operation - Day 2
28mLightning Talk: Cloud Native PostgreSQL - Running PostgreSQL on Kubernetes
31mLightning Talk: Kubernetes as Your DBA
20mNavigate Postgres Cloud Paths: Kubernetes, IaaS, or DbaaS
56mExperiments with Postgres in Docker and the Cloud
01h 02mDiamond Sponsor Hall
