In-Memory Cache across clouds
Managed Redis-compatible caches, provisioned with the network placement and failover settings already decided.
3 verified modules, 2 of them live-tested apply→verify→destroy; the rest are static-validated, live-test pending.
Compare by provider
| Provider | Module | Verification |
|---|---|---|
| AWS | ElastiCache for Redis / Valkey | ✓ live-tested |
| Azure | Azure Cache for Redis | static-validated |
| Google Cloud | Memorystore Redis/Valkey | ✓ live-tested |
How to choose
All three speak Redis, so choose by where the application runs - a cache one region away defeats its own purpose. After that the real decision is replicas and automatic failover, which is what separates the cheap single-node tier from a production one.
When not to use
A cache is not a database. Anything you cannot recompute should not live only here: eviction and failover both discard data by design, and neither is an incident.
Other solutions
Managed Relational Database18Managed Kubernetes15Virtual Machines13Messaging & Pub/Sub11Load Balancer10DNS & Traffic Management10Virtual Private Cloud (VPC)9Serverless Containers7Secrets & Key Management7Serverless Functions6Object Storage5API Gateway5Identity & Access5Container Registry3CDN & Edge Delivery3Monitoring & Observability3WAF & Edge Security3Shared File Storage3