|
|
|
|
|
|
by aftbit
848 days ago
|
|
|
Feature flags are one of those beautiful systems that are just expressive enough to be shoehorned into doing everything. Beta rollouts? Role-based auth? Billing entitelments? One-off customer requests? Yes. They can all be feature flags. The very best feature flags can optionally have a value attached to them. Then your API plan limits can just be feature flags. Now... is that the best way? Probably not, for any one of those use cases. But once you've built it, it is very tempting to use them for everything. |
|
|
I'm really interested in getting stronger opinions here about how to set people up for success. Being the founder of a feature flag company I feel like I'm a rope dealer.
I'm really interesting in providing good authorization primitives as well. This is kinda the whole reason/vision for why Prefab exists. If you have an authorization tool and a separate feature flag tool and a separate billing tool. You're going to be tempted to do some weird un-holy things. If you can use one provider for it, then we can really help when it comes to putting things in the right place. My dream is that you can type user.can_do?(:thing) and get back a response that has checked the authorization, ff & entitlements system and gives you a clear and comprehensible answer.