Skip to main content
This topic explains how the Runtime Delivery Network (RDN) works in the LaunchDarkly SDKs that support it, listed below. The Relay Proxy version 9.0 and later also supports RDN. RDN was previously called data saving mode. In SDK configuration, RDN is the data system. To use RDN, set the dataSystem configuration option. The exact name of the option varies by SDK, as shown in the examples in this topic.
RDN is opt-inSDKs don’t use RDN by default. To use it, update to an SDK version that supports RDN, then enable it in your SDK configuration as shown in the examples in this topic.
Server-side SDKs that use RDN first open a polling connection to LaunchDarkly. The initial payload from this connection contains the data the SDK needs to operate and perform flag evaluations. Subsequently, server-side SDKs that use RDN open a streaming connection and receive realtime flag configuration changes over the stream. These configuration changes include only the difference between the server-side SDK’s stored configuration and the latest configuration in LaunchDarkly. The SDKs use in-memory data for the unchanged aspects of the flag configuration. The SDKs fall back to using a polling connection if LaunchDarkly streaming is unavailable. RDN includes additional configuration options that let you set a backup data source, enabling automatic failover if a connection is unavailable. Depending on the number of flags in your project and the complexity of their configuration, RDN can significantly improve performance, including reducing your network costs when in polling mode or on reconnection. Additionally, SDKs that use RDN have reduced memory and CPU usage overall.
Track service connection usage by applicationWhen using RDN, you can track which applications are consuming service connections by configuring application metadata. Set the applicationId in your SDK configuration to see a per-application breakdown on the Service connections usage page under the SDK App ID dimension. Server-side streaming connections without applicationId configured appear as “Unknown.” To learn how, read Application metadata configuration.

Server-side SDKs

This feature is available in the following SDKs:
File initializers provide startup data but do not initialize the SDKWhen you configure a custom data source, a file initializer provides an initial set of flag data so your application can begin evaluating flags at startup. However, the SDK itself does not reach an initialized state from using the file initializer alone. The SDK is fully initialized only after it uses a streaming or polling synchronizer to connect to LaunchDarkly and obtain a complete set of flag data.The examples in this topic all pair a file initializer with a synchronizer. If you configure a file initializer without a synchronizer, your flags still load and evaluate correctly, but the SDK does not report itself as initialized. In this case, evaluate flags directly without gating your application’s startup on the SDK initialization status. As a best practice, we recommend not blocking application startup on SDK initialization in any configuration, so your application can start in a degraded but functional state and rely on fallback values until the SDK is ready.A file initializer reads the same file format as the file-based data source, including the flags and flagValues formats. To learn about the file format, read Reading flags from a file.

.NET (server-side)

To enable RDN:
  1. Upgrade the Relay Proxy to version 9.0 or later, if you use it.
  2. Upgrade your .NET (server-side) SDK to version 8.11 or later.
  3. Update your SDK configuration to enable the DataSystem configuration option.
Here’s how to enable the DataSystem configuration option:

Standard setup

We recommend the standard data system configuration for most customers. It uses a combination of streaming and polling to initialize the SDK, provide real time updates, and switch between streaming and polling automatically to provide redundancy.

Relay proxy with LaunchDarkly API fallback

File-based bootstrap with live updates

File-based bootstrap works in regulated or connectivity-restricted environmentsFile-based bootstrap works in production for organizations with compliance-driven restrictions on outbound connections to LaunchDarkly servers.If you use a file initializer in production, you must keep the file in sync with flag changes you make in the LaunchDarkly UI. LaunchDarkly does not update it for you.
To learn more, read DataSystemModes for information about pre-configured data system modes, and DataSystemBuilder for information on additional configuration options.

C++ (server-side)

To enable RDN:
  1. Upgrade the Relay Proxy to version 9.0 or later, if you use it.
  2. Upgrade your C++ (server-side) SDK to version 3.12 or later.
  3. Update your SDK configuration to enable the DataSystem configuration option.
The C++ SDK provides both a native C++ API and a C binding. The following examples show each.Here’s how to enable the DataSystem configuration option:

Standard setup

We recommend the standard data system configuration for most customers. It uses a combination of streaming and polling to initialize the SDK, provide real time updates, and switch between streaming and polling automatically to provide redundancy.

Relay Proxy with LaunchDarkly API fallback

To learn more, read DataSystemBuilder for information on additional configuration options.

Go

To enable RDN:
  1. Upgrade the Relay Proxy to version 9.0 or later, if you use it.
  2. Upgrade your Go SDK to version 7.11 or later.
  3. Update your SDK configuration to enable the DataSystem configuration option.
Here’s how to enable the DataSystem configuration option:

Standard setup

We recommend the standard data system configuration for most customers. It uses a combination of streaming and polling to initialize the SDK, provide real time updates, and switch between streaming and polling automatically to provide redundancy.

Relay proxy with LaunchDarkly API fallback

File-based bootstrap with live updates

File-based bootstrap works in regulated or connectivity-restricted environmentsFile-based bootstrap works in production for organizations with compliance-driven restrictions on outbound connections to LaunchDarkly servers.If you use a file initializer in production, you must keep the file in sync with flag changes you make in the LaunchDarkly UI. LaunchDarkly does not update it for you.
To learn more, read DataSystem. For information on additional configuration options, read DataSystemConfiguration.

Java

To enable RDN:
  1. Upgrade the Relay Proxy to version 9.0 or later, if you use it.
  2. Upgrade your Java (server-side) SDK to version 7.11 or later.
  3. Update your SDK configuration to enable the dataSystem configuration option.
Here’s how to enable the dataSystem configuration option:

Standard setup

We recommend the default data system configuration for most customers. It uses a combination of streaming and polling to initialize the SDK, provide real time updates, and switch between streaming and polling automatically to provide redundancy.

Relay proxy with LaunchDarkly API fallback

File-based bootstrap with live updates

File-based bootstrap works in regulated or connectivity-restricted environmentsFile-based bootstrap works in production for organizations with compliance-driven restrictions on outbound connections to LaunchDarkly servers.If you use a file initializer in production, you must keep the file in sync with flag changes you make in the LaunchDarkly UI. LaunchDarkly does not update it for you.
To learn more, read DataSystemModesfor information about pre-configured data system modes, and DataSystemBuilder for information on additional configuration options.

Node.js (server-side)

To enable RDN:
  1. Upgrade the Relay Proxy to version 9.0 or later, if you use it.
  2. Upgrade your Node.js (server-side) SDK to version 9.10 or later.
  3. Update your SDK configuration:
    • Enable the dataSystem configuration option.
    • Migrate existing LDOptions fields. The following existing options were previously top-level LDOptions fields and are part of the dataSystem configuration as of version 9.10: persistentStore, stream, streamInitialReconnectDelay, pollInterval, useLDD.
Here’s how to enable the dataSystem configuration option:

Standard setup

We recommend the standard data source option for most customers. It uses a combination of streaming and polling to initialize the SDK, provide real time updates, and switch between streaming and polling automatically to provide redundancy.

File-based bootstrap with live updates

File-based bootstrap works in regulated or connectivity-restricted environmentsFile-based bootstrap works in production for organizations with compliance-driven restrictions on outbound connections to LaunchDarkly servers.If you use a file initializer in production, you must keep the file in sync with flag changes you make in the LaunchDarkly UI. LaunchDarkly does not update it for you.
To learn more, read dataSystem. For information on additional configuration options, read LDDataSystemOptions.

Python

To enable RDN:
  1. Upgrade the Relay Proxy to version 9.0 or later, if you use it.
  2. Upgrade your Python SDK to version 9.13 or later.
  3. Update your SDK configuration to enable the DataSystem configuration option.
Here’s how to enable the DataSystem configuration option:

Standard setup

We recommend the standard data system configuration for most customers. It uses a combination of streaming and polling to initialize the SDK, provide real time updates, and switch between streaming and polling automatically to provide redundancy.

Relay proxy with LaunchDarkly API fallback

File-based bootstrap with live updates

File-based bootstrap works in regulated or connectivity-restricted environmentsFile-based bootstrap works in production for organizations with compliance-driven restrictions on outbound connections to LaunchDarkly servers.If you use a file initializer in production, you must keep the file in sync with flag changes you make in the LaunchDarkly UI. LaunchDarkly does not update it for you.
To learn more, read ldclient.datasystem. For information on additional configuration options, read DataSystemConfig.

Ruby

To enable RDN:
  1. Upgrade the Relay Proxy to version 9.0 or later, if you use it.
  2. Upgrade your Ruby SDK to version 8.12.0 or later.
  3. Update your SDK configuration to enable the data_system_config configuration option.
Here’s how to enable the data_system_config configuration option:

Standard setup

We recommend the standard data system configuration for most customers. It uses a combination of streaming and polling to initialize the SDK, provide real time updates, and switch between streaming and polling automatically to provide redundancy.

Relay proxy with LaunchDarkly API fallback

File-based bootstrap with live updates

File-based bootstrap works in regulated or connectivity-restricted environmentsFile-based bootstrap works in production for organizations with compliance-driven restrictions on outbound connections to LaunchDarkly servers.If you use a file initializer in production, you must keep the file in sync with flag changes you make in the LaunchDarkly UI. LaunchDarkly does not update it for you.
To learn more, read LaunchDarkly::DataSystem. To learn more about additional configuration options, read DataSystem::ConfigBuilder.

Rust

To enable RDN:
  1. Upgrade the Relay Proxy to version 9.0 or later, if you use it.
  2. Upgrade your Rust SDK to version 3.3 or later.
  3. Update your SDK configuration to enable the data_system configuration option.
Here’s how to enable the data_system configuration option:

Standard setup

We recommend the standard data system configuration for most customers. It uses a combination of streaming and polling to initialize the SDK, provide real time updates, and switch between streaming and polling automatically to provide redundancy.

Relay Proxy with LaunchDarkly API fallback

To learn more, read DataSystemBuilder for information on additional configuration options.

Client-side SDKs

Client-side SDKs that use RDN use the same data system pipeline as server-side SDKs, adapted to the lifecycle and connectivity characteristics of the client environment. SDKs may switch between connection modes automatically in response to application lifecycle events and network state changes. Some client-side SDKs use streaming when the application is active or in the foreground for real-time flag updates, and switch to polling or reduce activity when the application is backgrounded or hidden. This feature is available in the following SDKs:

Android

To enable RDN:
  1. Upgrade your Android Client SDK to version 5.13 or later.
  2. Update your SDK configuration to enable the dataSystem configuration option.
Here’s how to enable the dataSystem configuration option:

Standard setup

We recommend the standard data system configuration for most customers. It uses a combination of streaming and polling to initialize the SDK, provide real time updates, and switch between streaming and polling automatically to provide redundancy.

Automatic mode switching

The Android Client SDK switches between connection modes automatically based on app lifecycle and network connectivity. You can disable automatic switching entirely, or selectively disable lifecycle-driven or network-driven switching.To disable automatic switching entirely and keep the SDK in a single connection mode regardless of lifecycle or network changes:
To disable lifecycle-driven switching but continue switching modes when network connectivity changes:
To learn more, read Components.dataSystem(). To learn more about additional configuration options, read DataSystemBuilder.

Flutter

To enable RDN:
  1. Upgrade your Flutter SDK to version 4.20 or later.
  2. Update your SDK configuration to enable the dataSystem configuration option.
Here’s how to enable the dataSystem configuration option:

Standard setup

We recommend the standard data system configuration for most customers. The Flutter SDK uses streaming in the foreground for real-time flag updates and reduces activity in the background, and switches between connection modes automatically as the app moves between the foreground and background.

Set a fixed connection mode

To keep the SDK in a single connection mode instead of letting it manage the connection, set the initial connection mode. This applies as a sticky override that suppresses automatic mode switching until you clear it with setConnectionMode:
To learn more, read the launchdarkly_flutter_client_sdk API documentation.

JavaScript

To enable RDN:
  1. Upgrade your JavaScript SDK to version 4.9 or later.
  2. Update your SDK configuration to enable the dataSystem configuration option.
Here’s how to enable the dataSystem configuration option:

Standard setup

We recommend the standard data system configuration for most customers. The JavaScript SDK opens a streaming connection for real-time flag updates, and falls back to polling when streaming is unavailable.

Set a fixed connection mode

To keep the SDK in a single connection mode instead of letting it manage the connection, use manual mode switching and set the initial connection mode:

Send the context in the request body

By default, the SDK puts the evaluation context in the URL of each request. For streaming connections, this is because of a limit in the native browser EventSource. It can only send GET requests, and a GET request has no body, which means the context must go in the URL. To send the context in the request body instead, set the usePost configuration option to true. Use this option when you do not want the context to appear in the request URL.
The usePost option requires RDNThe usePost option is only available when RDN is on. To turn on RDN, set the dataSystem option.
For streaming connections, usePost also requires an EventSource implementation that supports custom HTTP methods. Set the eventSource configuration option to such an implementation. In v4.14 and later, LaunchDarkly provides an out-of-the-box implementation that supports POST. To learn how to use it, read the custom EventSource example, which shows a complete configuration with dataSystem and usePost. Without it, streaming requests use GET, polling requests still use POST, and the SDK logs a warning.The usePost option replaces useReport when you use the dataSystem option. The SDK ignores useReport and logs a warning in that case.
The usePost option is in early access. LaunchDarkly can change or remove it without notice.
To learn more, read LDOptions.dataSystem.

React Native

To enable RDN:
  1. Upgrade your React Native SDK to version 10.19 or later.
  2. Update your SDK configuration to enable the dataSystem configuration option.
Here’s how to enable the dataSystem configuration option:

Standard setup

We recommend the standard data system configuration for most customers. The React Native SDK uses streaming in the foreground for real-time flag updates and polling in the background, and switches between connection modes automatically as the app moves between the foreground and background.

Automatic mode switching

By default, the React Native SDK switches between connection modes automatically based on app lifecycle. To disable automatic switching entirely and keep the SDK in a single connection mode regardless of lifecycle changes:
To learn more, read LDOptions.dataSystem.

React Web

The React Web SDK is built on the JavaScript SDK and supports the same dataSystem configuration. Pass the option through the provider’s ldOptions.To enable RDN:
  1. Upgrade your React Web SDK to version 4.2 or later.
  2. Update your SDK configuration to enable the dataSystem configuration option.
Here’s how to enable the dataSystem configuration option:

Standard setup

We recommend the standard data system configuration for most customers. The React Web SDK opens a streaming connection for real-time flag updates, and falls back to polling when streaming is unavailable.

Set a fixed connection mode

To keep the SDK in a single connection mode instead of letting it manage the connection, use manual mode switching and set the initial connection mode:
To learn more, read LDReactClientOptions.

Vue

The Vue SDK relies on the JavaScript SDK for RDN and supports the same dataSystem configuration. Set the option in ldOptions when you install the plugin or create a provider.