Which plan to choose for Cache and Queues
Cache and Queues are managed services compatible with Redis clients and commands. For both, the plan's memory is the main resource: in Cache, it defines how much data is kept; in Queues, how many messages can wait for processing without putting pressure on the service.
Cache
Cache keeps data in memory to speed up the application: query results, sessions, external API responses and counters. The data can be discarded and recomputed, so the focus is speed, not durability.
| Plan | vCPU | RAM | Focus | Typical examples |
|---|---|---|---|---|
cache-free | 0.25 | 256 MiB | Get started at no cost | Prototype cache, sessions for a study project |
cache-starter | 0.5 | 512 MiB | Small projects and development environments | Login sessions, page cache for a small site |
cache-basic | 1 | 1 GiB | Growing applications | API query cache, per-user rate limiting |
cache-premium | 2 | 2 GiB | More data in memory, with metrics | Cache shared by several applications, real-time rankings and counters |
cache-enterprise | 8 | 8 GiB | Large volumes in memory | Platforms with many users and lots of hot data |
How to choose: estimate the size of what you want to keep and leave headroom. If the cache is always full and evicts keys that would still be useful, create a new Cache on a larger plan: a Cache's plan does not change after creation.
Queues
Queues receive tasks for asynchronous processing by workers, with persistent storage. The recommended pattern is Streams with consumer groups. See Managed queues.
| Plan | vCPU | RAM | Storage | Focus | Typical examples |
|---|---|---|---|---|---|
queue-free | 0.25 | 256 MiB | 1 GB fixed | Get started at no cost | Prototype queue, learning Streams and Pub/Sub |
queue-starter | 0.5 | 512 MiB | 5 GB, expandable | First production queues | Sending emails, processing webhooks |
queue-basic | 1 | 1 GiB | 5 GB, expandable | Production with high availability (one primary and two replicas) | E-commerce orders, file generation, integrations |
queue-premium | 2 | 2 GiB | 5 GB, expandable | More volume, with metrics | Many workers and producers, message spikes |
queue-enterprise | 8 | 8 GiB | 5 GB, expandable | Large message volume | Platforms with intense asynchronous processing |
How to choose: from queue-basic up, the queue has high availability, which matters when losing the processing of a message affects the customer. If messages pile up because workers cannot keep up, add workers before considering a larger plan for the queue.
Frequently asked questions
Can I use the same service as a cache and as a queue?
It is not recommended. Cache and Queues have different persistence and eviction settings. Use a Cache for disposable data and a Queue for tasks that must not be lost.
How many free services can I create?
Free Cache and Queues are limited to 1 per profile in each organization. See Limits and quotas.
Next steps
Last updated on
Which database plan to choose
What each Zenifra plan for PostgreSQL, MariaDB, Valkey Key-Value and Analytics is for, with examples of uses that make sense on each one.
Quick Start — Node.js
Publish a working Node.js application on Zenifra with Express, GitHub, configured port, and deployment validation.