Stigg has long provided ultra-low latency entitlement checks and fail-safe resilience when using our GraphQL-based SDKs. Today, we’re bringing those exact same high-availability features to developers integrating via REST!

With this release, customers leveraging REST-based SDKs can now benefit from < 10ms latency when performing entitlement checks by proxying requests through the Stigg Sidecar service.

🆕 What’s new?

REST-based SDKs can now benefit from the following:

• Sidecar Support: Install and deploy the Stigg Sidecar to proxy requests directly from REST-based SDKs.
• In-Memory & Persistent Caching: Configure the Sidecar service with a Redis instance to persistently cache entitlement and usage data locally across multiple nodes, or utilize out-of-the-box in-memory caching.
• Global Fallback Strategy: Configure the Sidecar service with a global fallback strategy for entitlement evaluations, ensuring default access rules apply even when data isn't cached.
• Offline Mode: Configure the Sidecar service to work in offline mode for local development and testing, allowing you to bypass Stigg API network requests entirely.

💡 Why it matters

• Sub-10ms Latency: REST API users can now resolve entitlement evaluations instantly from a local memory or Redis cache, reducing check latencies to under 10ms.
• Fail-Safe Resilience: Gain full offline resilience for your REST integrations. The Sidecar is engineered to keep serving entitlements even when the Stigg API is unreachable or network errors occur - serving cached entitlements, or fallback values for uncached ones.
• Streamlined Testing: With offline mode enabled, the Sidecar skips API key validation and limits entitlement evaluations strictly to your defined fallback values, turning other service methods into no-ops. This makes isolated testing and local development fast and predictable.

⚒️ Get started

1. Deploy the Stigg Sidecar as a shared service or alongside your main host application.
2. Provide your Sidecar deployment with connection details for your Redis instance to enable persistent caching, and/or configure default access rules using the ENTITLEMENTS_FALLBACK environment variable.
3. Update the configuration of the Stigg REST SDK to route requests through the local Sidecar proxy.

For detailed architecture diagrams and deployment instructions, check out our Stigg Sidecar Documentation.

📦 Availability

• REST is supported in the Sidecar service from v8.1.1 or later.
• Persistent caching is available for customers on the Stigg Scale plan.