3 ms·
Choosing a good solution heavily relies on whether your product is multi-tenant or not. If multi-tenant things get complicated quite quickly. It may be worth l
by throwaway38375 3y ago
Choosing a good solution heavily relies on whether your product is multi-tenant or not.
If multi-tenant things get complicated quite quickly. It may be worth looking into existing packages/libraries for your stack. I would be careful about using a third party service for this due to the latency it may introduce.
If not then just have a FEATURES constant. The value can be as primitive as an associative array, dict, hashmap, or struct. The keys are your flags and their values are booleans.
Not your forever choice, but very simple, quick, and easy to use.
- hahnbee 3y agoAh we're multi-tenant. In what ways do you feel like it gets complicated quickly?
- throwaway38375 3y agoBecause now you have different tenants having different experiences and breaking your application in strange new ways you could never have predicted!