For AI agents: The documentation index is at https://docs.digitalocean.com/llms.txt. Markdown versions of pages use the same URL with index.html.md in place of the HTML page (for example, append index.html.md to the directory path instead of opening the HTML document).

DigitalOcean MySQL Advanced Edition is the latest generation of Managed MySQL, with consensus-based replication for coordinated failover and a proxy for routing to the current primary.

MySQL Advanced Edition targets highly available workloads and supports vertical and horizontal scaling of database nodes as your workload grows.

High Availability Architecture

MySQL Advanced Edition runs MySQL on managed cluster nodes. The nodes participate in consensus-based replication, which tracks group membership, automatically elects the primary after failures, and coordinates failover.

MySQL Advanced Edition uses a proxy to provide clients with a single, stable service endpoint. The proxy sits in front of the database nodes, tracks which are healthy, and forwards traffic to the current primary. When the primary changes, it shifts routing so that the hostname and port can stay the same while the backing node changes.

During a failover, active connections to the former primary may be interrupted, but applications that reconnect to the same endpoint are routed to the new primary automatically.

Key Differences

The following table shows the key differences between MySQL Standard and Advanced Edition clusters.

Overview

Pricing

The Control Panel shows the total monthly cost when you create a cluster. Storage is billed at the same rate regardless of edition. Advanced Edition compute is priced higher than comparable Standard Edition plans, and your total depends on your plan and storage configuration. Pricing may change before general availability.

Features

• Vertical scaling: Resize nodes to a larger plan (more CPU, memory, or storage). The connection pooler manages traffic during the transition, reducing disruption.
• Horizontal scaling: Scale between 1-node and 3-node topologies only (2-node clusters are not supported).
• Physical backups: Backups use physical backup and restore, which improves reliability and performance for large datasets.

Availability

MySQL Advanced Edition is available in all regions.

Feedback and Support

MySQL Advanced Edition is in public preview. Public previews receive full support. We expect but do not guarantee that public previews perform for production-level workloads.

Our terms of service govern your use of DigitalOcean and cover details of eligibility, content, use, payments and billing, and warranties.

Usage of Advanced Edition during public preview is also subject to the Managed Databases Advanced Edition preview terms.

Create a MySQL Advanced Edition Cluster

To create a MySQL Advanced Edition cluster, go to the Databases page, then click Create Database.

Choose a Database Engine

On the Create Database Cluster page, under Choose a database engine, select MySQL. The database engine can’t be changed after creation.

Choose an Edition

Under Choose an edition, select Advanced Edition. The edition can’t be changed after creation.

Choose a Database Configuration

In the Choose a database configuration section, select one of the following options:

• General Purpose: Balanced vCPU-to-RAM ratio. Suitable for a broad range of workloads.
• Storage-Optimized: Higher RAM-to-vCPU ratio with more storage and concurrent connections. Recommended for most database workloads.

Under Select a plan, choose an option. Each option shows its combined monthly cost and included resources, such as vCPUs and memory.

After creation, you can increase your cluster’s compute size at any time.

Choose a Storage Size

In the Choose a storage size section, you can increase storage using the up arrow or by entering a value in 10 GiB increments, up to the maximum shown under Storage range.

After creation, you can increase storage at any time.

In the Autoscale storage section, select Enable Storage Autoscaling to automatically increase storage when disk utilization on any node in the cluster reaches the specified threshold. The threshold is based on the worst-performing node in the cluster, not the average across nodes. Click Customize to set a custom threshold and storage increment. The system bills this increase as additional storage.

Autoscaling takes several minutes, depending on the cluster size. It runs without downtime, and you do not need to take any action.

Choose a Datacenter Region

In the Choose a datacenter region section, select a datacenter for your cluster.

The list shows the datacenters where you currently have the most resources, with the number of resources shown to the right as X resources. Hover over this text to see the specific resources in that datacenter.

For the best performance, create your database in the same datacenter as your other DigitalOcean resources. After creation, you can relocate your cluster to another datacenter.

Finalize and Create

In the Finalize and Create section, enter a unique name for the cluster and select a project to add it to. After creation, you can move the cluster to another project, but its name can’t be changed.

When finished, click Create Database Cluster.

Clusters typically take five minutes or more to provision, but you can complete important configuration tasks such as restricting inbound connections while you wait.

Limitations

• Features, behavior, limits, and supported plans may change during the public preview.

• Advanced Edition currently does not support the following features that are available in Standard:

  • Online data import tool
  • Two-node cluster configurations

• Read scaling: MySQL Advanced Edition does not support dedicated read-only replicas for horizontal read scaling. Deployments are limited to a single-node cluster or a three-node cluster. All nodes in the cluster are active participants in the replication group, and any node may handle write traffic during failover. You cannot add read-only nodes outside the cluster, and because Advanced Edition has no standby nodes, the Standard Edition option to direct read traffic to standby nodes does not apply. As a result, read throughput is limited to the resources of the nodes in the deployment and cannot be scaled independently of cluster size.

• Point-in-time recovery (PITR) forking: You can create a new cluster from an existing cluster using PITR (forking). Forking a previously forked cluster (for example, parent to child to grandchild) is not supported in this release. To create additional forks, use the original source cluster as the starting point.

• Cross-region forking: Creating a cluster (fork) from a backup in a different region is not supported in this release.

• Firewall rules and forking: Firewall rules are not copied when you create a cluster using forking. The forked cluster uses default firewall settings. After creation, configure firewall rules on the new cluster as needed.