3 ms·
no-op point is true (except for logged out users - then the check is still useful) Anyway, how do you consistently decide to which 10% you show the new feature
by vemv 10y ago
no-op point is true (except for logged out users - then the check is still useful)
Anyway, how do you consistently decide to which 10% you show the new feature?
That piece of data is better stores in your Users table, as I see it. Plays well with authorization libs.
- pkaeding 10y agoThe way LaunchDarkly does it is to hash the user key, along with the feature key. This way the same users aren't always included in the '10% set' for all features, but they are consistently in the 10% set for a single feature. This also allows the decision to be made in memory, without an additional round-trip to the DB.