Build DigitalOcean Managed Database configurations for PostgreSQL, MySQL, Redis, and MongoDB.
Last verified: May 2026
Build DigitalOcean Managed Database configurations for PostgreSQL, MySQL, Redis, MongoDB, and Kafka with connection pools, replicas, and firewall rules.
Required Fields
nameengineregionsizenum_nodesOutput will appear here...The builder collects engine type, version, region, VPC, primary node size, standby/replica count, and pool configuration. It validates the version against currently-supported engines, checks node sizes against managed-database-eligible Droplet sizes, and emits a `digitalocean_database_cluster` Terraform block plus any `digitalocean_database_replica` and `digitalocean_database_connection_pool` blocks. Trusted sources are emitted as `digitalocean_database_firewall` resources.
DigitalOcean Managed Databases handle backups, point-in-time recovery, version upgrades, and standby replicas — at a price premium over self-managed Postgres on a Droplet, justified by not getting paged for the database at 3am. The DO Managed Database Config Builder generates a complete spec including engine, version, node size, region, primary/standby/read-replica topology, connection pool configuration, and trusted source firewall rules.
Your app's connection count to the Postgres primary has been creeping toward the configured max_connections ceiling, with periodic 'too many connections' errors during traffic spikes. You add a transaction-mode connection pool through the builder, point the app at the pool host instead of the database directly, and the connection count to the actual database drops from 380 to under 50 — even though the app side is still opening hundreds of pooled connections. The 'too many connections' alerts stop the same day.
Always enable the standby node for production. The price difference is meaningful (~50% over single-node) but the operational difference is enormous — automatic failover, no single point of failure, and the standby is also the read source for any continuous backup verification.
Use transaction-mode pooling for serverless and short-lived workloads; use session-mode pooling for traditional long-lived connections from app servers. Mixing modes from the same app is fine if you have a clear understanding of which queries hold transactions across statements.
PostgreSQL, MySQL, Redis, MongoDB, OpenSearch, and Kafka. PostgreSQL and MySQL are the most mature offerings with the broadest version and feature support. Redis offers persistent and non-persistent modes; MongoDB is a managed Mongo cluster; OpenSearch is for full-text search; Kafka is the newest addition.
DigitalOcean's managed connection pool is built on PgBouncer (for Postgres) and exposes the standard session and transaction pooling modes. It runs in DO's infrastructure between your app and the database, removing the need to self-host PgBouncer. For very high connection volume or specialized routing, you may still want a self-hosted PgBouncer in front of the managed pool, but for most workloads the built-in pool is sufficient.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.