LoginSign Up
← Back to all sparks
LaunchDarkly logo

LaunchDarkly

INFRA · APIS
Velocity0.0

Feature management and experimentation platform

launchdarkly.com ↗

LaunchDarkly is moving experiment analysis into the customer's own warehouse.

warehouse-native-experimentationfeature-flagssdk-rewritedata-governanceflag-safety
◆Current state
April's work runs on two tracks. Warehouse-native experimentation reached both Redshift and Databricks within a day of each other, letting teams run experiments in LaunchDarkly while metrics compute inside their own warehouse, with automated health checks added for those connections. Separately, the React SDK shipped a ground-up v4 rewrite on the new JavaScript client, and flags gained the ability to restore a previous version from change history.
◆Where it's heading
The experimentation story is the one that matters. Rather than pulling customer event data into LaunchDarkly to analyse it, LaunchDarkly is computing where the data already lives — which sidesteps the data-movement and governance objections that stall experimentation platforms in larger companies. Shipping Redshift and Databricks back to back, then immediately adding connection health checks, is the pattern of a capability being made operational rather than demonstrated.
◆Prediction
Expect the remaining major warehouses to follow the same integration pattern, and more tooling around connection reliability as the warehouse becomes a dependency in the experiment path. The SDK rewrite suggests the other client SDKs will be consolidated onto the same JavaScript core.

◆Recent moves

  1. 3mo ago

    React Web SDK documentation page for the v4 rewrite

    The React Web SDK docs, captured with the v4 release notes pasted into its title. It duplicates the v4.0.0 entry rather than announcing anything separately.

    View source ↗
  2. 3mo ago

    React SDK v4.0.0

    The React SDK is rebuilt on the new JavaScript client SDK, targeting React 19 and moving into the js-core monorepo so it stays aligned with the other JavaScript SDKs. A maintenance-driven major version rather than new functionality, but it resets the SDK's foundation.

  3. 3mo ago

    Databricks Native Experimentation Integration

    Warehouse-native experimentation extends to Databricks, one day after the Redshift integration. Experiments are configured in LaunchDarkly while results are analysed in the customer's own warehouse, continuing the push to leave the data where it sits.

  4. 3mo ago

    Redshift Native Experimentation Integration

    Amazon Redshift becomes a warehouse-native experimentation target, computing metrics inside the customer's warehouse. It opens the pair of integrations that define this window.

  5. 3mo ago

    Warehouse Health Checks

    Automated health checks for warehouse connections, arriving just before the Redshift and Databricks integrations. Unglamorous, but it is what makes an external warehouse safe to have in the experiment path.

  6. 4mo ago

    Restore Previous Flag Version

    A previous version of a flag can be restored directly from its history, making unintended targeting changes reversible. Straightforward safety tooling for the core flag product while the platform work happens elsewhere.