How to Convert Caching Databases to Valkey
Validated on 24 Apr 2025 • Last edited on 24 Apr 2025
Valkey is a high-performance, open-source database that stores key-value data in memory, and is designed for caching, message queues, and primary database use. Fully compatible with Redis, Valkey serves as a drop-in replacement.
DigitalOcean Managed Caching is approaching its end of availability (EOA). You cannot create new Caching clusters past 30 April 2025 (except if you already have an existing Caching cluster), and the product will be discontinued on 30 June 2025.
To replace Managed Caching, we are now offering Managed Valkey, a Redis-compatible alternative that offers RDMA and higher throughput.
All Managed Caching clusters will automatically convert to Valkey clusters by 30 June 2025 during your upgrade window, retaining all data. You can also manually convert your Caching cluster to Valkey using the control panel or the DigitalOcean API.
Convert Using the Control Panel
To manually convert your Caching cluster using the control panel, go to the Databases page and click on your Caching cluster.
In the banner at the top of the page, click Upgrade database to Valkey to begin the conversion process.
Convert Using the API
To manually convert your Caching cluster using the API, make a PATCH request to /databases/{uuid}/cluster_type with the following format:
curl -X PATCH \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
-d '{"cluster_type": "valkey"}' \
"https://api.digitalocean.com/v2/databases/9cc10173-e9ea-4176-9dbc-a4cee4c4ff30/cluster_type"