Skip to main content
Deploy the Sidecar either as a classic sidecar pattern (one per service or pod) or as a small shared service, scaling horizontally based on load. When using only in-memory cache, adding more replicas may increase cache misses since each instance maintains its own independent cache. For improved hit ratios and resilience, use Redis with the persistent cache service.

​
Persistent Cache

Run the persistent-cache-service to maintain Redis synchronization. This service consumes a Stigg-managed SQS queue and keeps Redis up to date with the latest entitlement data. The service is stateless and horizontally scalable. Prerequisites: Stigg-provisioned SQS queue and your own Redis instance.

​
Offline and fallback behavior

When the Stigg API is unreachable, SDKs and the Sidecar return results from their local cache or apply fallback strategies to keep your application operational. Usage data can be buffered and optionally persisted to disk, preventing data loss during extended outages.