Managed Database

Dear DigitalOcean Support and Product Team, Our application has been hosted on DigitalOcean since inception, using MariaDB as our primary datastore. As our platform expands, we are actively transitioning our workloads to DigitalOcean Kubernetes (DOKS) to modernize deployment and scaling. However, the absence of a Managed MariaDB offering within DigitalOcean’s Database-as-a-Service (DBaaS) portfolio creates a serious operational hurdle. While Managed MySQL is available, modern MariaDB has diverged considerably in syntax, storage engines, JSON handling, and system-versioned tables, making a conversion to MySQL risky and resource-intensive. At the same time, deploying and self-hosting stateful MariaDB clusters inside Kubernetes introduces significant DevOps overhead, storage management complexity, and backup maintenance that counteract the benefits of running a managed cloud infrastructure. This challenge reflects a broader pattern across emerging small-to-medium enterprises (SMEs) and startup engineering teams. Many growing companies deliberately standardize on MariaDB over MySQL to operate within an open, community-led ecosystem under the MariaDB Foundation, insulating themselves from Oracle’s complex commercial licensing, proprietary plugin policies, and long-term governance uncertainties. As open-source independence becomes a strategic priority for engineering roadmaps, relying exclusively on Oracle MySQL leaves a noticeable gap in DigitalOcean's database catalog. Supporting MariaDB natively aligns with the needs of developers who require open database governance without sacrificing cloud-managed simplicity. Introducing Managed MariaDB with automated patching, automated backups, and high-availability node failover would directly address this gap and strengthen DigitalOcean’s developer-first positioning. It would eliminate friction for growing teams scaling into DOKS, preventing users from routing their database layer to external cloud providers or taking on the operational burden of persistent volume management in-cluster. We strongly urge the database and product teams to consider adding managed MariaDB instances to the roadmap, and we appreciate your consideration of this feedback. Sincerely, DIPROIT PVT. LTD. Sri Lanka.

"Connection pooling is not supported for MySQL." https://docs.digitalocean.com/products/databases/mysql/ (see also: https://aws.amazon.com/rds/proxy

It would be nice to be able to use MariaDB as a managed database on DO in addition to MySQL, as it provides some features that MySQL does not, and it receives more frequent updates.

Please let us active wal_compression to increase the throughput

Tiger Data (timescale) have launched the perfect extension for text search with strong maintainer, features and ease of use Please add suport for pg_textsearch

DuckDB has just launched a new pg_duckdb extension and I want to use it in my PostgreSQL database to improve the performance in analytics. pg_duckdb is a Postgres extension that embeds DuckDB's columnar-vectorized analytics engine and features into Postgres. The GitHub repo: https://github.com/duckdb/pg_duckdb

Postgres 18+ comes with OAuth 2.0 support: https://www.postgresql.org/docs/current/auth-oauth.html We have an existing IdP that supports OAuth 2.0 and being able to use it for auth would be much more secure than having to manage usernames and passwords.

It would be useful for some applications to have this open source database: https://github.com/ClickHouse/ClickHouse

Please allow configuration of io_method=io_uring Or set io_uring as default

Add support for proper db user isolation, it should be initially in the managed db, just creating users with read/write only is not good enough.