You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 30, 2023. It is now read-only.
Implement push updates to feature flag values cached in the SDK memory.
🎤 Why is this feature needed ?
Currently, the update mechanism is based on polling with a given interval, it makes flag values stale till the next polling interval. In cases where freshness matters or cases where SDK on one machine triggers value updates and the rest are out of sync, using push updates will result in all machines being synchronized and near real-time freshness.
✌️ How do you aim to achieve this?
Make use of GraphQL subscriptions (WebSockets) to broadcast feature value changes to relevant (those of the tenant whose values have been changed) SDK instances.
🔄️ Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?
🔖 Feature description
Implement push updates to feature flag values cached in the SDK memory.
🎤 Why is this feature needed ?
Currently, the update mechanism is based on polling with a given interval, it makes flag values stale till the next polling interval. In cases where freshness matters or cases where SDK on one machine triggers value updates and the rest are out of sync, using push updates will result in all machines being synchronized and near real-time freshness.
✌️ How do you aim to achieve this?
Make use of GraphQL subscriptions (WebSockets) to broadcast feature value changes to relevant (those of the tenant whose values have been changed) SDK instances.
🔄️ Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?
Are you willing to submit PR?
None
ENR-70
The text was updated successfully, but these errors were encountered: