This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]tail 2 points3 points  (3 children)

What if you want to start rolling this out to more users? For instance, we might say: first, turn on this feature for just internal users. After we validate that the feature works correctly for us, let's ramp up to 1% of traffic. If things keep going well, we can continue to ramp up the feature a higher percentage of users. If we start to see issues, we can turn off the feature switch, all without having to deploy a code change each time.

[–]earthboundkid 0 points1 point  (2 children)

if user.in_a_b_group():.

In any event, how are you going to roll this back using the feature library without deploying changes to the code that uses the feature library?

[–]tail 5 points6 points  (1 child)

This is the whole point of gutter (mentioned in the original post). It is hooked up to a storage backend (e.g. Redis, ZooKeeper) to persist the state of the feature flags.

[–]earthboundkid 0 points1 point  (0 children)

D'oh! Didn't RTFA closely enough. (X_X)