Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A/B testing and similar "conditional loading" scenarios #104

Open
technosophos opened this issue Aug 6, 2021 · 1 comment
Open

A/B testing and similar "conditional loading" scenarios #104

technosophos opened this issue Aug 6, 2021 · 1 comment

Comments

@technosophos
Copy link
Contributor

Today Brendan suggested a feature that I think would be really cool:

He suggested "dyanmic overrides packaged as part of the request." He's thinking along the lines of Launch Darkly or A/B testing frameworks.

In the simplest case, you could merely select which module to run based on host headers. But Brendan suggested taking it even further and being able to specify a module in an HTTP header and have that loaded in the request (think like a Bindle reference where the runtime could verify the integrity of the package before loading).

Probably, we can start with loading conditionally off of a Bindle + HTTP header or A/B flag cookie. Then we could work out this second part.

@itowlson
Copy link
Contributor

If we're still interested in features like this, we need to form a sense for how we want this stuff to compose and layer. We could certainly push this in at the WAGI layer, but does it truly belong there, or in Hippo, or in some intermediate layer (which might mean further splitting out the core WAGI engine from the configuration and routing layer)...?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants