Navigate Postgres Cloud Paths: Kubernetes, IaaS, or DbaaS
summary
Enterprises move to cloud for agility and lower lock‑in and one customer reports 52 days to provision now needing hours not weeks. VMs plus Ansible fail NIST cloud tests—no rapid elasticity or measured service. Kubernetes gets closer but lacks a control plane and shared responsibility model and requires a level‑4/5 operator. EDB demonstrates a working pattern: a Postgres operator with Azure Resource Manager tied by a control plane that reacts to software and hardware events.
AI-written summary · about
chapters (9)
- 0:00Intro
- 2:25Why are enterprises moving to the cloud?
- 5:58Why are enterprises leaving legacy databases?
- 7:38Postgres as the clear winner in the database game
- 10:26Cloud Provider Service Models
- 10:50Essential characteristics of a Cloud Service Model
- 14:49What is missing from Kubernetes?
- 16:03Cloud Native Postgres Kubernetes Clusters
- 17:56Navigating Postgres in the cloud
related talks
54mPostgres: From Cloud to Hybrid and On Prem Again
25mPostgres on Kubernetes for the Reluctant DBA
26mBeyond the DBaaS Trap: Achieving Data Sovereignty With Kubernetes and CloudnativePG
37mData On Kubernetes, Deploying And Running PostgreSQL And Patterns For Databases In a Kubernetes Cluster.
30mBridging the DevOps to Data Divide with a Common Cloud Native Stack
50mDemystifying Kubernetes for Postgres DBAs; A Guide to Operators
51mPostgreSQL in the Cloud: DBaaS vs Kubernetes
28mFrom VMs to Ku...