Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client Side Caching #2854

Draft
wants to merge 5 commits into
base: master
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions packages/client/index.ts
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,9 @@ import RedisSentinel from './lib/sentinel';
export { RedisSentinelOptions, RedisSentinelType } from './lib/sentinel/types';
export const createSentinel = RedisSentinel.create;

import { BasicClientSideCache, BasicPooledClientSideCache } from './lib/client/cache';
export { BasicClientSideCache, BasicPooledClientSideCache };

// export { GeoReplyWith } from './lib/commands/generic-transformers';

// export { SetOptions } from './lib/commands/SET';
Expand Down
64 changes: 64 additions & 0 deletions packages/client/lib/client/README-cache.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,64 @@
# Client Side Caching Support

Client Side Caching enables Redis Servers and Clients to work together to enable a client to cache results from command sent to a server and be informed by the server when the cached result is no longer valid.

## Usage

node-redis supports two ways of instantiating client side caching support

Note: Client Side Caching is only supported with RESP3.

### Anonymous Cache

```javascript
const client = createClient({RESP: 3, clientSideCache: {ttl: 0, maxEntries: 0, lru: false}})
```

In this instance, the cache is opaque to the user, and they have no control over it.

### Controllable Cache

```javascript
const ttl = 0, maxEntries = 0, lru = false;
const cache = new BasicClientSideCache(ttl, maxEntries, lru);
const client = createClient({RESP: 3, clientSideCache: cache});
```

In this instance, the user has full control over the cache, as they have access to the cache object.

They can manually invalidate keys

```javascript
cache.invalidate(key);
```

they can clear the entire cache
g
```javascript
cache.clear();
```

as well as get cache metrics

```typescript
const hits: number = cache.cacheHits();
const misses: number = cache.cacheMisses();
```

## Pooled Caching

Similar to individual clients, node-redis also supports caching for its pooled client object, with the cache being able to be instantiated in an anonymous manner or a controllable manner.

### Anonymous Cache

```javascript
const client = createClientPool({RESP: 3}, {clientSideCache: {ttl: 0, maxEntries: 0, lru: false}, minimum: 8});
```

### Controllable Cache

```javascript
const ttl = 0, maxEntries = 0, lru = false;
const cache = new BasicPooledClientSideCache(ttl, maxEntries, lru);
const client = createClientPool({RESP: 3}, {clientSideCache: cache, minimum: 8});
```
Loading