Data
Early accessManaged cache
Fast in-memory caching to speed up your apps, kept private in Canada.
Keep frequently used data in memory so your apps respond faster and your database does less work. Choose a basic cache, or a replicated one that switches sites automatically if one fails.
Opens to early-access customers in later waves. Not yet generally available.
Features
Redis or Memcached
Choose a Redis-compatible or Memcached-compatible cache; both are created, connected and monitored the same way.
Basic or replicated
A basic cache empties on restart; a replicated one keeps a copy in a second site and switches over automatically.
Shared caching and sessions
Every copy of your app shares one cache and session store, so users stay signed in as you scale.
Rate limits, locks and messages
Share request limits, short-lived locks and quick messages across every copy of your app.
Right-sized, with clear metrics
Pick a size and what to remove when full, resize later, and track usage to size on evidence.
Private and separate per environment
Only your private network can connect, encrypted, and each environment gets its own cache, so tests never touch production.
How it works
- 1
Choose an engine, tier and size in your region and province.
- 2
Connect it to your apps; each environment gets its own cache.
- 3
Use your usual caching libraries over your private, encrypted network.
ata cache create catalog --engine redis --version 7.2 --size medium --ha --eviction-policy allKeysLru --persistence appendOnly \
--isolation perEnvironment --region ca-east --residency ON --sites 2 # TLS only
ata cache connect catalog --app storefront --role readWrite # per-app ACL user and token source on each environment's instance
ata cache failover catalog --env staging # rehearse a site failover; clients keep the same endpointSovereignty
Cached data and replicas stay in the Canadian sites and province you choose, and failover happens only between them.