| name | use-cache-bulk |
| description | Bulk reads/writes via cache.many(keys[]) → values[] (nulls for misses, order preserved) and cache.setMany(record, ttl?) → void. Triggers: `cache.many`, `cache.setMany`, "get multiple keys at once", "batch read cache", "warm the cache", "preload many keys", "mget", "mset"; typical import `import { cache } from "@warlock.js/cache"`. Skip: tag-based bulk invalidation — `@warlock.js/cache/use-cache-tags/SKILL.md`; single-key ops — `@warlock.js/cache/cache-basics/SKILL.md`; competing libs `ioredis` `MGET`/`MSET`. |
Bulk operations — cache.many / cache.setMany
Read or write a batch of keys in one call instead of awaiting them one at a time.
Read many — many(keys)
import { cache } from "@warlock.js/cache";
const [alice, bob, carol] = await cache.many(["user.1", "user.2", "user.3"]);
- Returns an array positionally aligned with
keys.
- Missing keys come back as
null (same as get), so the result length always
equals the input length — zip them back together by index.
const ids = [1, 2, 3];
const users = await cache.many(ids.map((id) => `user.${id}`));
const missingIds = ids.filter((_, index) => users[index] === null);
Write many — setMany(items, ttl?)
await cache.setMany({
"user.1": alice,
"user.2": bob,
"user.3": carol,
}, 3600);
- Keys are the object keys; values are the object values.
- The optional second arg is a single TTL (seconds) applied to all entries —
there's no per-entry TTL or
tags knob here. When you need tags or mixed TTLs,
loop with cache.set and
the rich options object instead.
Performance note
On every driver these run their underlying get/set calls concurrently
(Promise.all) on the shared connection; on the memory family it's effectively
instant. There's no partial-failure handling — if one write rejects, the
returned promise rejects.
See also
