package module
Version: v1.1.1 Latest Latest

This package is not in the latest version of its module.

Go to latest
Published: Apr 7, 2022 License: Apache-2.0 Imports: 15 Imported by: 1


LaunchDarkly Server-side SDK for Go - Dynamodb integration

Circle CI Documentation

This library provides a DynamoDB-backed persistence mechanism (data store) for the LaunchDarkly Go SDK, replacing the default in-memory data store.

This version of the library requires at least version 5.3.0 of the LaunchDarkly Go SDK. In Go SDK versions prior to 5.0.0, the lddynamodb package was built into the SDK (gopkg.in/launchdarkly/go-server-sdk.v4/lddynamodb).

The minimum Go version is 1.14.

For more information, see also: Using DynamoDB as a persistent feature store.

Quick setup

This assumes that you have already installed the LaunchDarkly Go SDK.

  1. Import the LaunchDarkly SDK packages and the package for this library:
import (
    ld "gopkg.in/launchdarkly/go-server-sdk.v5"
    lddynamodb "github.com/launchdarkly/go-server-sdk-dynamodb"
  1. When configuring your SDK client, add the DynamoDB data store as a PersistentDataStore. You may specify any custom DynamoDB options using the methods of DynamoDBDataStoreBuilder. For instance:
    var config ld.Config{}
    config.DataStore = ldcomponents.PersistentDataStore(
            SessionOptions(session.Options{Profile: "profile_name"}),

By default, the DynamoDB client will try to get your AWS credentials and region name from environment variables and/or local configuration files, as described in the AWS SDK documentation.

Caching behavior

The LaunchDarkly SDK has a standard caching mechanism for any persistent data store, to reduce database traffic. This is configured through the SDK's PersistentDataStoreBuilder class as described the SDK documentation. For instance, to specify a cache TTL of 5 minutes:

    var config ld.Config{}
    config.DataStore = ldcomponents.PersistentDataStore(

Data size limitation

DynamoDB has a 400KB limit on the size of any data item. For the LaunchDarkly SDK, a data item consists of the JSON representation of an individual feature flag or segment configuration, plus a few smaller attributes. You can see the format and size of these representations by querying https://sdk.launchdarkly.com/flags/latest-all and setting the Authorization header to your SDK key.

Most flags and segments won't be nearly as big as 400KB, but they could be if for instance you have a long list of user keys for individual user targeting. If the flag or segment representation is too large, it cannot be stored in DynamoDB. To avoid disrupting storage and evaluation of other unrelated feature flags, the SDK will simply skip storing that individual flag or segment, and will log a message (at ERROR level) describing the problem. For example:

    The item "my-flag-key" in "features" was too large to store in DynamoDB and was dropped

If caching is enabled in your configuration, the flag or segment may still be available in the SDK from the in-memory cache, but do not rely on this. If you see this message, consider redesigning your flag/segment configurations, or else do not use DynamoDB for the environment that contains this data item.

This limitation does not apply to target lists in Big Segments.

A future version of the LaunchDarkly DynamoDB integration may use different strategies to work around this limitation, such as compressing the data or dividing it into multiple items. However, this integration is required to be interoperable with the DynamoDB integrations used by all the other LaunchDarkly SDKs and by the Relay Proxy, so any such change will only be made as part of a larger cross-platform release.

LaunchDarkly overview

LaunchDarkly is a feature management platform that serves over 100 billion feature flags daily to help teams build better software, faster. Get started using LaunchDarkly today!

About LaunchDarkly

  • LaunchDarkly is a continuous delivery platform that provides feature flags as a service and allows developers to iterate quickly and safely. We allow you to easily flag your features and manage them from the LaunchDarkly dashboard. With LaunchDarkly, you can:
    • Roll out a new feature to a subset of your users (like a group of users who opt-in to a beta tester group), gathering feedback and bug reports from real-world use cases.
    • Gradually roll out a feature to an increasing percentage of users, and track the effect that the feature has on key metrics (for instance, how likely is a user to complete a purchase if they have feature A versus feature B?).
    • Turn off a feature that you realize is causing performance problems in production, without needing to re-deploy, or even restart the application with a changed configuration file.
    • Grant access to certain features based on user attributes, like payment plan (eg: users on the ‘gold’ plan get access to more features than users in the ‘silver’ plan). Disable parts of your application to facilitate maintenance, without taking everything offline.
  • LaunchDarkly provides feature flag SDKs for a wide variety of languages and technologies. Read our documentation for a complete list.
  • Explore LaunchDarkly



Package lddynamodb provides a DynamoDB-backed persistent data store for the LaunchDarkly Go SDK.

For more details about how and why you can use a persistent data store, see: https://docs.launchdarkly.com/sdk/features/storing-data/dynamodb#go

To use the DynamoDB data store with the LaunchDarkly client:

import lddynamodb "github.com/launchdarkly/go-server-sdk-dynamodb"

config := ld.Config{
    DataStore: ldcomponents.PersistentDataStore(lddynamodb.DataStore("my-table-name")),
client, err := ld.MakeCustomClient("sdk-key", config, 5*time.Second)

By default, the data store uses a basic DynamoDB client configuration that is equivalent to doing this:

dynamoClient := dynamodb.New(session.NewSession())

This default configuration will only work if your AWS credentials and region are available from AWS environment variables and/or configuration files. If you want to set those programmatically or modify any other configuration settings, you can use the methods of the lddynamodb.DataStoreBuilder returned by lddynamodb.DataStore(). For example:

config := ld.Config{
    DataStore: ldcomponents.PersistentDataStore(

Note that CacheSeconds() is not a method of lddynamodb.DataStoreBuilder, but rather a method of ldcomponents.PersistentDataStore(), because the caching behavior is provided by the SDK for all database integrations.

If you are also using DynamoDB for other purposes, the data store can coexist with other data in the same table as long as you use the Prefix option to make each application use different keys. However, it is advisable to configure separate tables in DynamoDB, for better control over permissions and throughput.



This section is empty.


This section is empty.


This section is empty.


type DataStoreBuilder

type DataStoreBuilder struct {
	// contains filtered or unexported fields

DataStoreBuilder is a builder for configuring the DynamoDB-based persistent data store.

This can be used either for the main data store that holds feature flag data, or for the big segment store, or both. If you are using both, they do not have to have the same parameters. For instance, in this example the main data store uses the table "table1" and the big segment store uses the table "table2":

config.DataStore = ldcomponents.PersistentDataStore(
config.BigSegments = ldcomponents.BigSegments(

Note that the builder is passed to one of two methods, PersistentDataStore or BigSegments, depending on the context in which it is being used. This is because each of those contexts has its own additional configuration options that are unrelated to the DynamoDB options.

Builder calls can be chained, for example:

config.DataStore = lddynamodb.DataStore("tablename").SessionOptions(someOption).Prefix("prefix")

You do not need to call the builder's CreatePersistentDataStore() method yourself to build the actual data store; that will be done by the SDK.

func DataStore

func DataStore(tableName string) *DataStoreBuilder

DataStore returns a configurable builder for a DynamoDB-backed data store.

The tableName parameter is required, and the table must already exist in DynamoDB.

func (*DataStoreBuilder) ClientConfig

func (b *DataStoreBuilder) ClientConfig(config *aws.Config) *DataStoreBuilder

ClientConfig adds an AWS configuration object for the DynamoDB client. This allows you to customize settings such as the retry behavior.

func (*DataStoreBuilder) CreateBigSegmentStore added in v1.1.0

func (b *DataStoreBuilder) CreateBigSegmentStore(
	context interfaces.ClientContext,
) (interfaces.BigSegmentStore, error)

CreateBigSegmentStore is called internally by the SDK to create a data store implementation object.

func (*DataStoreBuilder) CreatePersistentDataStore

func (b *DataStoreBuilder) CreatePersistentDataStore(
	context interfaces.ClientContext,
) (interfaces.PersistentDataStore, error)

CreatePersistentDataStore is called internally by the SDK to create a data store implementation object.

func (*DataStoreBuilder) DescribeConfiguration

func (b *DataStoreBuilder) DescribeConfiguration() ldvalue.Value

DescribeConfiguration is used internally by the SDK to inspect the configuration.

func (*DataStoreBuilder) DynamoClient

DynamoClient specifies an existing DynamoDB client instance. Use this if you want to customize the client used by the data store in ways that are not supported by other DataStoreBuilder options. If you specify this option, then any configurations specified with SessionOptions or ClientConfig will be ignored.

func (*DataStoreBuilder) Prefix

func (b *DataStoreBuilder) Prefix(prefix string) *DataStoreBuilder

Prefix specifies a prefix for namespacing the data store's keys.

func (*DataStoreBuilder) SessionOptions

func (b *DataStoreBuilder) SessionOptions(options session.Options) *DataStoreBuilder

SessionOptions specifies an AWS Session.Options object to use when creating the DynamoDB session. This can be used to set properties such as the region programmatically, rather than relying on the defaults from the environment.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL