This SDK supports both cloud bucketing (requests outbound to https://bucketing-api.devcycle.com) as well as local bucketing (requests to a local bucketing engine self-contained in this SDK).

go get "github.com/devcyclehq/go-server-sdk/v2"

package main
import "github.com/devcyclehq/go-server-sdk/v2"

    sdkKey := os.Getenv("DVC_SERVER_KEY")
	user := devcycle.User{UserId: "test"}

	options := devcycle.Options{
		EnableEdgeDB:                 false,
		EnableCloudBucketing:         false,
		EventFlushIntervalMS:         0,
		ConfigPollingIntervalMS:      10 * time.Second,
		RequestTimeout:               10 * time.Second,
		DisableAutomaticEventLogging: false,
		DisableCustomEventLogging:    false,
	}

	client, _ := devcycle.NewClient(sdkKey, &options)

To find usage documentation, visit our docs.

This SDK is supported by our test harness, a test suite shared between all DevCycle SDKs for consistency.

Unit tests can be run with the standard Go testing tools, or with make test. They are run automatically on PRs with the Go race detector enabled. To reproduce this locally, run with RACE=1 make test. Some race detector errors might only show up on Github actions due to differences in how quickly tests are executed.

Configuration of the SDK is done through the Options struct.

By default, logging is disabled to avoid overhead and noise in your logs. To enable it for debugging the SDK, set the devcycle_debug_logging build tag when compiling your project:

go build -tags devcycle_debug_logging ...

The following options are available when you are using the SDK in Cloud Bucketing mode.

The following options are available when you are using the SDK in Local Bucketing mode.

This SDK also supports a version of the DevCycle bucketing and segmentation logic built using WASM.

To activate the WASM bucketing library, include the following build tag for your application:

-tags devcycle_wasm_bucketing

This implementation is still under-going active development. Take care when utilizing it in production environments.

We run golangci/golangci-lint on every PR to catch common errors. You can run the linter locally via the Makefile with:

make lint

Lint failures on PRs will show comments on the "Files changed" tab inline with the code, not on the main Conversation tab.