You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if there was some way for a backend to integrate with OpenReplay as well that controls feature flags. An example of a potential use case would be a kill switch. Say we want to disable email sending entirely. Yes, we would want to disable that functionality on the frontend, but if there are 3rd party systems that integrate with that same backend and we want to stop all email sending, then the backend also should know the state of that feature flag to be able to respond properly to it's consumers. This could be maintained in multiple systems, but it's harder to maintain and more fragile.
The text was updated successfully, but these errors were encountered:
It's a custom spring boot application, but I could see a use case for any number of backends. I see that there are already some robust APIs exposed. I imagine there would be a new API or an expansion of the Projects API that exposes the available feature flags. The one sticking point in my mind would be how the flags that are scoped to certain users would appear for service to service communication.
It would be great if there was some way for a backend to integrate with OpenReplay as well that controls feature flags. An example of a potential use case would be a kill switch. Say we want to disable email sending entirely. Yes, we would want to disable that functionality on the frontend, but if there are 3rd party systems that integrate with that same backend and we want to stop all email sending, then the backend also should know the state of that feature flag to be able to respond properly to it's consumers. This could be maintained in multiple systems, but it's harder to maintain and more fragile.
The text was updated successfully, but these errors were encountered: