This is the Go Server Side SDK for the feature management platform featureflag.co. It is intended for use in a multiple-users Go server applications.
This SDK has two main purposes:
- Store the available feature flags and evaluate the feature flags by given user in the server side SDK
- Sends feature flags usage, and custom events for the insights and A/B/n testing.
We use websocket to make the local data synchronized with the server, and then store them in the memory by default. Whenever there is any changes to a feature flag or his related data, the changes would be pushed to the SDK, the average synchronization time is less than 100 ms. Be aware the websocket connection can be interrupted by any error or internet interruption, but it would be restored automatically right after the problem is gone.
In the offline mode, SDK DOES not exchange any data with featureflag.co
In the following situation, the SDK would work when there is no internet connection: it has been initialized in
using ffc.InitializeFromExternalJson(json)
function
To open the offline mode:
config := ffc.NewConfigBuilder().
SetOffline(false).
Build()
client = ffc.NewClient(envSecret, config)
SDK will initialize all the related data(feature flags, segments etc.) in the bootstrapping and receive the data updates in real time, as mentioned in the above
After initialization, the SDK has all the feature flags in the memory and all evaluation is done locally and synchronously, the average evaluation time is < 10 ms.
Applications SHOULD instantiate a single instance for the lifetime of the application. In the case where an application needs to evaluate feature flags from different environments, you may create multiple clients, but they should still be retained for the lifetime of the application rather than created per request or per thread.
The bootstrapping is in fact call this function ffc.NewClient(envSecret, config)
, in which the SDK will be
initialized, using streaming from featureflag.co.
client = ffc.NewClient(envSecret, config)
if(client.IsInitialized()){
// do whatever is appropriate
}
Note that the sdkKey(envSecret) is mandatory.
FFCConfig
exposes advanced configuration options for the FFCClient
.
startWaitTime
: how long the constructor will block awaiting a successful data sync. Setting this to a zero or negative
duration will not block and cause the constructor to return immediately.
offline
: Set whether SDK is offline. when set to true no connection to feature-flag.co anymore
We strongly recommend to use the default configuration or just set startWaitTime
or offline
if necessary.
// default configuration
config = ffc.DefaultFFCConfig()
client = ffc.NewClient(envSecret, config)
SDK calculates the value of a feature flag for a given user, and returns a flag vlaue/an object that describes the way that the value was determined.
FFUser
: A collection of attributes that can affect flag evaluation, usually corresponding to a user of your application.
This object contains built-in properties(key
, userName
, email
and country
). The key
and userName
are required.
The key
must uniquely identify each user; this could be a username or email address for authenticated users, or a ID for anonymous users.
The userName
is used to search your user quickly. All other built-in properties are optional, you may also define custom properties with arbitrary names and values.
client = ffc.NewClient(envSecret, config)
// FFUser creation
ffcUser := model.NewFFUserBuilder().
UserName("userName").
Country("country").
Email("email").
Custom("key", "value").Build()
// be sure that SDK is initialized
// this is not required
if(client.IsInitialized()){
// Evaluation details
flagtStatue :=client.VariationDetail("featureFlagKey",ffcUser,"defaultValue")
// Flag value
res := client.Variation("flag key", ffcUser, "Not Found");
// get all variations for a given user
userTags :=client.GetAllLatestFlagsVariations(ffcUser)
}
If evaluation called before Java SDK client initialized or you set the wrong flag key or user for the evaluation, SDK will return
the default value you set. The FlagState
and AllFlagStates
will all details of later evaluation including the error reason.
SDK support the String, Boolean, and Number as the return type of flag values, see JavaDocs for more details.