Introducing remote attributes
We’ve rolled out remote attributes to make Bucket faster and easier to implement. Company and user attributes stored on our servers can now be used when evaluating feature flags.
The introduction of remote attributes means that rather than having to fetch or compute all the required attributes each time a feature flag is evaluated, you only need to provide the Company ID and User ID when fetching features.
Attributes in Bucket are updated when they change, via the SDK, or periodically from your backend via the API.
Like so:
With remote attributes you can:
- Set the
company planattribute according to the customer subscription plan from your backend and then gate features access based on the plan from anywhere in your application. - Use an attribute called
betaUser: trueto gate who gets access to beta features. Then allow users to opt-in to beta features using a button in your application that simply sets the attribute in Bucket. - Integrate with your back office system to set a list of the add-ons that the customer has bought through an attribute in Bucket. For example:
addOns: [‘copilot-addon’, ‘ sso’]which you can then use in feature targeting.
Company and user attributes stored in Bucket are automatically used when evaluating feature flags in the case of our browser-based SDKs and can optionally be used in the server-based SDKs.
Setting remote attributes is a simple method call using our Node SDK. You can also set attributes through our Segment integration which allows you to continue using your existing setup.
By default, attributes are replicated to multiple locations across the globe in our global infrastructure to keep initial evaluation round-trip times low.
However, you have the option to keep your data exclusively within the EU if you need to adhere to certain data protection regulations.
Happy shipping!