Managed database

A managed database is a database service the cloud provider operates for you: they run the servers, patching, backups, replication, and failover, while you keep full control of the schema, queries, and data. You trade a higher sticker price for far less operational work.

A managed database is a database service the cloud provider operates for you. They handle the servers, operating system, patching, backups, replication, and failover; you keep full control of the schema, queries, users, and data. You trade some control and a higher sticker price for far less operational work.

In plain terms

It’s the difference between owning a car and taking a taxi: same destination, someone else does the maintenance. Instead of running PostgreSQL yourself on a virtual machine and owning every 2 a.m. failover, you run the same PostgreSQL on Amazon RDS or Aurora, Azure Database for PostgreSQL (or Azure SQL for SQL Server workloads), or Google Cloud SQL. Same engine, same drivers, same SQL; the pager duty moves to the provider.

Why it matters when you migrate

  • It’s the most common replatform win. Swapping a self-managed database for the managed equivalent is the classic first step beyond lift-and-shift: minimal code change, large operational payoff. The move itself is covered in migrating a production database.
  • High availability becomes a checkbox. Multi-zone failover and point-in-time restore are built in, replacing clustering work that takes real expertise to run well on your own.
  • Compare total cost, not sticker price. The instance costs 30 to 80% more than raw compute, but the honest comparison includes the engineer hours you no longer spend on patching, backups, and failover drills.