Implementing Feature Toggle

[aburakab]

What is the recommended approach to do Feature Toggle implementation in Abp?
Keep in mind that I might have a temporary feature toggles that is available in Release 1 and I might remove it in Release 2 or 3.
Also I have some business Feature toggles, so I might have a feature which requested by two clients; But I want to ship it with Logic A for the 1st client and with Logic B for 2nd client (Looks like it's a DI/IoC thing). But I would like to hear from you?

[hikalkan]

ABP doesn't offer a solution for this yet. I don't know their names, but you may find some libraries on the web or you can implement your own logic.

We can take this as a feature request to work on for next versions.

[hikalkan]

I see that Microsoft did something: https://github.com/microsoft/FeatureManagement-Dotnet (see document: https://docs.microsoft.com/en-us/azure/azure-app-configuration/use-feature-flags-dotnet-core)

[aburakab]

Do you think that ABP should adopt it as is?

[hikalkan]

I haven't tried it yet. However, it will direct work when you follow the Microsoft's document. You can use it today. When we work on this issue, we will try to understand if it would be good if we do something with the ABP Framework.

[angelieri]

I use a simple implementation.
A table to registry the feature and what user or customer is changed
Features
UserID - Number
Feature - Varchar

Then in my new feature process we do sometrhing like this:

if (Beta.IsBeta(UserID, Feature))
{
Do process A
}
else
{
Do process B
}

Beta.Isbeta uses cache.
Feature list is a enumeration.

[balessi75]

Voting for this to be considered in a future release

[elovelan]

There's a relatively new standard, similar to OTel, called OpenFeature that might also be worth a look. There's even a discussion on the Microsoft.FeatureManagement repo about trying to unify them.