Databases in the Cloud

Self-managed on a VM

You can install PostgreSQL, MySQL, or another engine on a virtual machine. You control versions and extensions, but you also own patching, backups, failover, and disk growth.

Managed database services

Managed offerings (for example Amazon RDS/Aurora, Azure Database, Cloud SQL) run the engine for you. You still design schemas and queries; the provider handles much of the operational overhead. You trade some deep control for convenience and often better default durability.

Decide with trade-offs

• Choose managed when you want automated backups and easier HA
• Choose self-managed when you need unusual engines, extensions, or full OS access
• Keep databases in private subnets; do not expose them to the open internet
• Match region and AZ strategy to your app for latency and resilience

Remember data gravity

Databases accumulate state. Moving them later is harder than moving stateless web tiers. Pick region, encryption, and backup policy thoughtfully from the start.