We're excited to share the general availability of support for persistent entitlement caching using Redis in the Stigg Node.js SDK.

By default, the Node.js SDK caches entitlement data in-memory to reduce the latency on subsequent entitlement checks. This approach is usually suffice when only one process or service is responsible for accessing the entitlement data.

By configuring the Node.js SDK to leverage a Redis server for caching, entitlement data becomes persistent, is synchronized even when accessed by multiple services and processes, and survives restarts. 

Persistent caching can also greatly reduce the latency of entitlement checks in application that leverage a serverless infrastructure, where each process is transient and can be de-provisioned after a limited period of time.

Persistent caching using Redis is supported by the Stigg Node.js SDK v0.7.5 or later. To enable it, please contact the Stigg Support Team.

More details about Stigg's persistent caching implementation can be found here.