Using flipper as permanent feature control #725
-
Hi, when reading through Flipper documentation, I see that it's mostly designed to be used as something temporal. But I was wondering if it's also used a a way to permanently control what users can access what features. Is it discouraged, or a well supported use case? I understand that in general it's not designed to be used with thousands of actors in mind. My basic idea was that users belong to companies, and companies have a "plan". And a plan is composed by multiple features. Maybe using plans as actors would be a solution? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Nope. I do it all the time. It's my favorite thing about flipper. I use it for permanent, long-lived features at least as much as temporary roll outs. I wouldn't do thousands of actors per feature, but you are welcome to try. You'll likely want to turn off preloading (but leave memoization on). That'll ensure you are only loading all those actors for the features being checked. You are also in luck that we've just done several performance rounds to make loading lots of actors faster (active record adapter). It's likely that what you are trying to do may be a little odd right now, but would be much easier once we get expressions #557 launched. We don't currently have a timeline for it but are hoping May/June. |
Beta Was this translation helpful? Give feedback.
Nope. I do it all the time. It's my favorite thing about flipper. I use it for permanent, long-lived features at least as much as temporary roll outs.
I wouldn't do thousands of actors per feature, but you are welcome to try. You'll likely want to turn off preloading (but leave memoization on). That'll ensure you are only loading all those actors for the features being checked.
You are also in luck that we've just done several performance rounds to make loading lots of actors faster (active record adapter).
It's likely that what you are trying to do may be a little odd right now, but would be much easier once we get expressions #557 launc…