3 ms·
A/B Testing for a K:V, key(“button-color”) = “red” for 10%, “green” for 90% In a Enterprise, where there are multiple teams wanting to manage their own K:V sto
by prjed 6y ago
A/B Testing for a K:V, key(“button-color”) = “red” for 10%, “green” for 90%
In a Enterprise, where there are multiple teams wanting to manage their own K:V store, having a global K:V is helpful. Also being able to refer to a project to refer to their K:V
if key(“price”) = “100” is set in Global and one of the projects is setting it again to a different val or same show a warning that you’re rewriting that.
- jeremyis 6y agoGot it! For A/B testing, we have that on our roadmap, though I think you could implement a poor man's version like this: K:V would be: testing_data: { exposure: 0.10, colors: ['green', 'red'], } // on the client: function getColor() { configly.get('testing_data, function(data) { const roll = Math.random(); const index = roll > data['exposure'] ? 0 : 1; return data['colors'][index]; }); } re: global K:V. We plan on introducing teams that would work exactly that way! Thanks!