4 ms·

Features that would be nice to have: A/B Testing, Global config keys so Enterprise customers can use them across projects. Is there a size limit, do clients do

by prjed 6y ago

Features that would be nice to have: A/B Testing, Global config keys so Enterprise customers can use them across projects. Is there a size limit, do clients download changes or entire file?

jeremyis 6y ago
Hi! Thanks so much for your comment! Could you expand a bit on what you'd like with A/B testing? All of the values can be fetched across projects / clients, it's essentially a simple K:V store with broad libraries. For example, if you have a key "price" whose value is a number "100", you can call: configly.get(price) from all your clients (provided they are all using the same API KEY). Today, clients download at the granularity of an entire key-value. So if you changed that price to "150", it'd fetch the entirety of "150" and not just the digit flip. Were you envisioning a case of storing a lot of data? Today, our free service is capped at 100kb total. Was there a use case you had in mind?
- 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 ago
    Got 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!

by prjed 6y ago

Features that would be nice to have: A/B Testing, Global config keys so Enterprise customers can use them across projects. Is there a size limit, do clients download changes or entire file?

jeremyis 6y ago

Hi! Thanks so much for your comment! Could you expand a bit on what you'd like with A/B testing? All of the values can be fetched across projects / clients, it's essentially a simple K:V store with broad libraries. For example, if you have a key "price" whose value is a number "100", you can call: configly.get(price) from all your clients (provided they are all using the same API KEY). Today, clients download at the granularity of an entire key-value. So if you changed that price to "150", it'd fetch the entirety of "150" and not just the digit flip. Were you envisioning a case of storing a lot of data? Today, our free service is capped at 100kb total. Was there a use case you had in mind?

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 ago
  Got 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!