This page provides you with the following information about Memorystore for Memcached:
- Key points and dates for the deprecation of this Memorystore service
- The Memorystore services that we recommend you use
Key points and dates
This section contains key points and dates for the deprecation of Memorystore for Memcached.
- On January 20, 2026, Memorystore for Memcached will no longer be a recommended Memorystore service in Google Cloud.
- After February 1, 2027, you can't create Memorystore for Memcached instances in new projects unless these instances already exist in these projects.
- On January 31, 2029, Cloud Customer Care for Memorystore for Memcached will end. After this date, you'll no longer be able to use Memorystore for Memcached.
Recommendations
We recommend that you use this migration guide to migrate your workloads to Memorystore for Valkey. Memorystore for Valkey provides you with similar functionality to Memorystore for Memcached. In addition, Memorystore for Valkey has the following benefits:
- It offers a fully managed, high-performance, in-memory datastore for Valkey, a Redis-compatible, open-source project.
- It's a fully managed Valkey service for Google Cloud, which supports both Cluster Mode Enabled and Cluster Mode Disabled instances.
- Your applications that run on Google Cloud can achieve extreme performance by leveraging the highly scalable, available, secure Valkey service without the burden of managing complex Valkey deployments.
In addition to Memorystore for Valkey, you can migrate to the following Memorystore services:
- Memorystore for Redis: a fully managed Redis service for Google Cloud. Applications running on Google Cloud can achieve extreme performance by leveraging this highly scalable, available, secure service without the burden of managing complex Redis deployments.
- Memorystore for Redis Cluster: this Memorystore service has all of the features and benefits of Memorystore for Redis. However, to ensure high availability, Memorystore for Redis Cluster also distributes (or shards) your data across primary nodes and can replicate your data across optional replica nodes. The service's horizontally scalable cluster architecture provides better performance than a vertically scalable architecture because Redis' performance is better on many smaller nodes than on fewer larger nodes.