Memorystore for Redis
Database as a service (DBaaS) providers
Database software
- Features
- Ease of use
- Ease of management
- Quality of support
- Affordability
- Market presence
Take the quiz to check if Memorystore for Redis and its alternatives fit your requirements.
Pay-as-you-go
Free Trial
Free version unavailable
Small
Medium
Large
- Media and communications
- Arts, entertainment, and recreation
- Accommodation and food services
What is Memorystore for Redis
Memorystore for Redis is a fully managed Redis service on Google Cloud used primarily for in-memory caching, session storage, and low-latency data access. It targets application teams that want Redis-compatible functionality without operating their own clusters. The service integrates with Google Cloud networking, IAM, monitoring, and automation workflows. It is typically used alongside primary databases rather than as a system of record.
Fully managed Redis operations
Google Cloud handles provisioning, patching, maintenance, and monitoring for Redis instances. This reduces operational work compared with self-managed Redis deployments on virtual machines. It also standardizes common tasks such as backups and instance resizing through the cloud console, CLI, and APIs.
Low-latency in-memory performance
The service is designed for in-memory workloads where predictable low latency is important, such as caching, leaderboards, rate limiting, and session management. It supports Redis data structures and common access patterns used by application developers. This makes it a practical complement to general-purpose DBaaS platforms that prioritize persistence over sub-millisecond access.
Google Cloud integration controls
Memorystore integrates with Google Cloud VPC networking and IAM-based access controls, aligning with centralized cloud governance. It works with Google Cloud monitoring and logging tooling for operational visibility. These integrations can simplify deployment in organizations standardizing on Google Cloud infrastructure.
Narrow scope versus databases
Memorystore is optimized for caching and transient data rather than durable, relational, or analytical storage. It is not a replacement for a primary database and typically requires pairing with another data store for persistence and complex querying. Teams looking for broader database features may need additional services and data synchronization patterns.
Google Cloud platform dependency
The managed service is tied to Google Cloud’s infrastructure, APIs, and operational model. This can increase switching costs for organizations pursuing multi-cloud portability or on-premises parity. Network design and access patterns also depend on Google Cloud VPC constructs.
Redis feature parity constraints
As a managed offering, some advanced Redis operational behaviors and configurations may be constrained compared with running Redis directly. Certain extensions, modules, or highly customized tuning may not be available depending on service tier and supported versions. This can matter for teams with specialized Redis deployments or strict version/module requirements.
Plan & Pricing
| Plan | Price | Key features & notes |
|---|---|---|
| Basic | Default (USD, per 1 GiB hour, region shown on page - Iowa/us-central1): M1 (1–4 GiB) $0.049 / GiB·hr; M2 (5–10 GiB) $0.027 / GiB·hr; M3 (11–35 GiB) $0.023 / GiB·hr; M4 (36–100 GiB) $0.019 / GiB·hr; M5 (>100 GiB) $0.016 / GiB·hr. (Committed use discounts available: 1-year and 3-year reduced rates shown on official pricing page.) | Standalone Redis instance. Charged by provisioned capacity (GiB) in 1-second increments; capacity tiers determine performance. Prices vary by region. |
| Standard | Default (USD, per 1 GiB hour, region shown on page - Iowa/us-central1): M1 (1–4 GiB) $0.064 / GiB·hr; M2 (5–10 GiB) $0.054 / GiB·hr; M3 (11–35 GiB) $0.046 / GiB·hr; M4 (36–100 GiB) $0.035 / GiB·hr; M5 (>100 GiB) $0.03 / GiB·hr. (Committed use discounts available: 1-year and 3-year reduced rates shown on official pricing page.) | Highly available Redis instance with automatic cross-zone replication and automatic failover. Supports read replicas (M2+); read replicas increase node count and charges. Network egress charged separately; inter-region egress per GiB varies by source region. |
Additional pricing notes:
- Billing: charged based on provisioned capacity (GiB) in 1-second increments; you incur charges when an instance is created even if unused. (Official pricing page.)
- Committed Use Discounts (CUD): 1‑year and 3‑year reduced rates are published per capacity tier on the official pricing page.
- Network egress: example inter-region egress rates on the official page include $0.02/GB within North America, $0.08/GB to other continents, etc.; region-specific egress table available on the official pricing page.
- Pricing varies by region; the pricing page provides region selector and Cloud Platform SKU equivalents.
Seller details
Google LLC
Mountain View, CA, USA
1998
Subsidiary
https://cloud.google.com/deep-learning-vm
https://x.com/googlecloud
https://www.linkedin.com/company/google/
