Consider changing the default value of refreshInterval so it is less spammy #247
Comments
|
Hi @rcjsuen, the refresh interval is configurable via options: https://docs.getunleash.io/reference/sdks/javascript-browser#available-options. In general, 30 seconds is the best we've found. I can understand it might be a problem if you have a massive amount of clients, but in those cases we see people being detailed-oriented and tweaking these configurations. But for small setups it works well and can be adapted as you scale. We're also trying to align and standardize our default refresh intervals, but based on the current setup of different SDKs: https://docs.getunleash.io/reference/sdks#client-side-sdks-1 I'm inclined to think that 30s is going to be our default. I'll close this, as I feel this resolves the question, but feel free to re-open or respond if you want to follow up. And thanks for the feedback! I'll make sure our team is aware of it. |
Describe the feature request
unleash-proxy-client-js/src/index.ts
Line 180 in 3c994f0
Currently, this library uses a default of 30s for the
refreshInterval. If you just move ahead with the defaults (without thinking much about it) and release your code, you may end up getting a swarm of requests to your backend. Would Unleash consider changing the default to 60s or 5m or whatever else seems "reasonable" (although I completely understand that "reasonable" is subjective).I understand that there's another side to the coin here. You want to refresh regularly so that if something goes wrong you want to be able to change the state of a flag quickly to protect your users as soon as possible.
Background
No response
Solution suggestions
No response
The text was updated successfully, but these errors were encountered: