Reliable entitlement evaluation depends on fast, consistent access to entitlement data, which is why Stigg provides both local and persistent caching mechanisms to keep entitlement checks performant and resilient.
To make entitlement checks fast and reliable, Stigg SDKs cache a customer’s entitlements locally in memory. This avoids repeated network calls and ensures your application can continue evaluating entitlements even if the Stigg API is temporarily unreachable. The cache stays up to date through periodic polling, or through real-time updates for backend SDKs.In-memory caching is ideal for most applications, but for large fleets or serverless environments where processes restart often, Stigg also supports a persistent external cache (such as Redis). A persistent cache keeps entitlements available across restarts, reduces cache misses, and further lowers latency for entitlement checks.
For large distributed systems or serverless environments where processes restart frequently, Stigg supports a persistent external cache (e.g., Redis). Persistent caching keeps entitlements available across restarts, reduces cache misses, and ensures consistent entitlement data across all instances of your application.Stigg provides a dedicated persistent cache setup (supported in the Node SDK and Sidecar) that syncs entitlement and usage updates to your Redis cluster in near real time. This approach offers several advantages:
Entitlement data remains available even during API outages
Lower latency and fewer direct API calls
Reduced memory footprint in each service instance
Higher cache hit rates and fewer coherence issues across fleets
To enable persistent caching, your environment must run the persistent-cache-service, which consumes entitlement update messages from Stigg and keeps your Redis cache current.
