https://www.growthbook.io/ logo
Join Slack
Powered by
This message was deleted.
# announcements
w
This message was deleted.
f
Hi Nishchal, I think that would be useful to others. We've talked about building something similar ourselves. There are some additional things we were thinking of adding to the proxy server eventually such as websocket support (so clients can get feature updates streamed to them), and server-side evaluation of feature flags (so rules don't have to be exposed to the front-end). Happy to collaborate on this, or if you want to build a V1 quickly yourself, we can figure out later how we can extend it.
h
we can follow the scooter analogy, We start with v1 with simple service which acts as a proxy, we can do a new feature release with websocket for people who want it 🙂 while maintaining backwards compatibility.
although for the proxy to evaluate server side, I hated the amplitude because it'd mean so much of talking to experiment-service per request, that it won't be ideal We'd have to think about things like error handling, latency, timeouts, circuit breaking etc, I don't think having SSR evaluation is a good idea. The current implementation of what we want, there's absolutely 0 chance of anything going wrong 🙂 because everything is local evaluation. web socket to listen to changes is actually a good idea 🙂 we can certainly give options for other people to decide for themselves, it'd help generate clients for languages which we don't support yet 🙂
f
Yeah, agreed. I think SSR evaluation is useful for certain situations so it's a good option to have, but I definitely wouldn't make it mandatory.
h
do you have a place where I can add a design document or something?
I'll give this a stab 🙂
https://cyberhck.notion.site/Design-Document-Growthbook-Proxy-afd54d4e6d7c4794889337abacf1fc4c wow, when you need to worry about other people's setup, it sure does get a lot harder 😄 I'm thinking of a redis dependency 🙂
143 Views
Open in Slack
PreviousNext
Powered by