Open vikhyat187 opened 1 year ago
Some thoughts
Instead of putting all these details in the issue, let's use wiki?
Feature flag data model should have a description attribute.
Will add description attribute
User - FF mapping is needed at all times for the client side. Also required for the dashboard, is when you want to search for a user and check what all feature flags are enabled for them.
Yes, we want to search if the flag is enabled for the user. @ankushdharkar mentioned if we can have some way in which reading is very fast, writing can consume some time. (This is optional)
FF - User mapping is interesting and depends on where it might be used. Dashboards? Do we really want to list all the users on a particular FF? There could be thousands. How do we effectively show them on screen? Search? why not just search using the user id then?
Yes, possibly I can think of dashboards, true they can be thousands of users, let's have the scope by searching by user id for now.
Approach 1
Feature Flag
Users (Existing)
FeatureFlagUserMapping
Approach 2: storing flags in Users
Feature Flag
Users (Existing)
Approach 3: Storing Users in Feature flags and Flags in Users
Feature Flag
Users (Existing)