Cache work you do repeatedly
Store frequently accessed results and set expiry times from your application. Choose an eviction policy that fits the way your cache is used.
Key Value
Keep shared state
within easy reach.
Give your applications a Redis-compatible service for caches, sessions and job queues. Connect privately, choose an eviction policy and manage capacity alongside the rest of your stack.
Your code. Infrastructure included.
Web application
Background worker
app-cache / Key Value
Shared state.Redis-compatible. Privately connected.
session:8a92EX 3600catalog:featuredEX 300queue:receiptsLISTYour application. Your keys.
Redis compatibleUse familiar application clients
Private connectionConnect your apps and workers
Your policyConfigure key eviction behavior
KEY VALUE ON OPENSTEAD
A shared layer for applications that do more.
Connect your web app and background workers to the same Key Value service. Use your preferred library to decide what to cache, how long to keep it and how jobs move.
Connect background jobs
Use a compatible queue library to hand work from web services to workers. Keep the broker and consumers on the same private environment network.
Manage state deliberately
Key Value uses append-only persistence and supports database backups. Select memory capacity and monitor consumption as your keys and workload change.
MADE FOR YOUR STACK
A Redis connection, with your application in control.
Use a standard Redis client and the private URL from your console. Your cache keys, expiry times and job semantics stay in your application code.
- Credentials are supplied through the service connection details.
- Append-only persistence is enabled for stored data.
- Memory and eviction settings should match cache or queue requirements.
A shared application cacheopenstead / configuration
NODE.JS EXAMPLEimport { createClient } from "redis";
const cache = createClient({
url: process.env.REDIS_URL,
});
await cache.connect();
await cache.set("catalog:featured",
JSON.stringify(products), { EX: 300 });Install a compatible Redis client. Set REDIS_URL using your Key Value service’s private connection details.
PUT IT TO WORK
Built for the work
your application does.
Application caching
Cache expensive queries, repeated API responses or computed values with appropriate expiry times.
Session storage
Share server-side session state between application processes using your framework’s Redis integration.
Queue backends
Connect Celery, BullMQ or another compatible library to a broker your web app and workers can both reach.
HOW IT WORKS
One connection. Several useful jobs.
Create the service
Add Key Value to your project. Select a resource plan and configure an eviction policy for the workload.
Connect your clients
Copy the private connection URL into the environment of each web service or worker that needs access.
Set the rules in your app
Choose key expiry, queue retry behavior and client connection limits. Watch memory usage as traffic and data grow.
Can I use my existing Redis library?
Key Value runs Redis and supports compatible Redis clients. Check your client and library requirements for the Redis version used by the service.
Is a worker included with Key Value?
The Key Value service supplies the shared data or broker layer. Create a separate background worker to consume jobs using your queue library.
Which eviction policy should I choose?
Choose a policy suited to the data. A cache may discard old keys, while a queue must avoid losing pending jobs to eviction. Follow your queue library’s configuration requirements and size memory for the workload.
Can I back up Key Value data?
Yes. Key Value supports scheduled and manual backups and restoration into a separate service. Your application should still define how to recover or rebuild cache data and how to handle repeated jobs.
MAKE YOUR NEXT MOVE
Give your applications something in common.
Your code. Infrastructure included.