First Experiences with Azure Database for PostgreSQL Flexible Server
summary
Hands-on Azure Flexible Server deployment for MB.OS uses Terraform 2.91.0 and Azure DevOps pipelines, provisioning consolidated Postgres instances on Linux (Postgres 11–13), adding PgBouncer, Log Analytics for logs, and Terraform dynamic blocks to toggle zone‑reduant HA or burstable SKUs per environment. Burstable consolidation yields about 86% cost reduction for dev, BYOK is not yet supported so initial use is dev-only, CLI/metric names differ from Single Server, maintenance windows can be scheduled, and observed failovers are typically ~40s of reconnection time.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:11Mercedes Benz operating system
- 6:21Azure Database for Postgres – Single Server
- 8:52Improvements with Flexible Server
- 12:00Provisioning
- 16:55Operational aspects of network security
- 18:11Creating databases
- 19:37Server logs
- 20:21Scripting & monitoring
- 21:39Costs
- 23:43Zone redundant HA
- 30:01Next steps
- 30:47Q&A with Johannes & Claire
related talks
25mWhat’s New with Azure Database for PostgreSQL- Flexible Server
50mUnleashing the Power of Azure for PostgreSQL
32mWhat makes Azure Database for PostgreSQL Great for Developers?
26mWhat Enterprises like about Azure Database for PostgreSQL - Flexible Server
56mSeamless Migration to Azure Database for PostgreSQL
35mDeploying PostgreSQL to Azure with Bicep
31mBuild scalable and secure enterprise apps on OSS databases Q&A
27mAzure AD authentication with PostgreSQL Flexible Servers