πBeta functionality
Supporting beta features is not that hard. Let's do it!
We have built in a "beta functionality" concept that is propagated from feature toggles into our services. This is a catch-all for new features that we want to test, and which may not yet be ready for wider release. This means that our services need to have distinct checks for this, though.
As you can see in the next section on feature toggles, we can also use user groups to segment features, as well as classic, individual toggles that can be used on a per-user basis.
What gives? Aren't these beta features just like any other toggles? Yes. In this project, we define βbeta featuresβ as a feature-level, wide bucket across user groups, while user grouping is a dynamically wide bucket (basically just audience segmentation). This way, we can define granularly both user groups and on beta usage.
π― Example: See for example src/FakeUser/usecases/createFakeUser.ts
that uses the provided toggles when calling the User entity which dynamically creates different types of users from this toggle.
Last updated