Skip to main content
This guide will help you migrate from the legacy Java/Kotlin Server SDK to the new Java Core SDK. The Java Core SDK offers significant performance improvements and new features, as it’s built on a shared Rust core library.

Why Migrate?

  • Performance: Java Core achieves faster evaluation times and lower CPU consumption, making it more efficient than the legacy SDK.
  • New Features: Access to Parameter Stores, CMAB (Contextual Multi-Armed Bandits), observabilityClient, and more
  • Future Support: All new features and improvements will only be available in Java Core
  • Maintenance: The legacy Java SDK is in maintenance mode and will only receive critical bug fixes

Installation Differences

Legacy Java/Kotlin SDK

Java Core SDK

Java Core requires both the core library and a platform-specific native library:
To determine the correct platform-specific dependency, you can run this code:
This will output the appropriate dependency for your system.

API Differences

Key Package and Class Changes

Initialization

Checking Gates

Getting Configs

Getting Experiments

Getting Layers

Logging Events

Configuration Options Differences

Migration Steps

  1. Update Dependencies
    • Replace com.statsig:serversdk with com.statsig:javacore
    • Add the platform-specific dependency
  2. Update Imports
    • Replace import com.statsig.sdk.* with import com.statsig.*
  3. Update Initialization
    • Change from static methods to instance methods
    • Use the builder pattern for options and StatsigUser
    • Replace new StatsigUser("user_id") with new StatsigUser.Builder().setUserID("user_id").build()
    • Initialize with new Statsig(key, options) and call initialize()
  4. Update User Creation
    • Use the builder pattern: new StatsigUser.Builder().setUserID("user_id").build()
  5. Update Method Calls
    • Replace static methods with instance methods
    • Remove Sync suffix from method names
    • Update method signatures as needed
  6. Test Thoroughly
    • Verify all feature gates, experiments, and configs work as expected
    • Check that event logging is functioning correctly
  1. Update Dependencies
    • Replace com.statsig:serversdk with com.statsig:javacore
    • Add the platform-specific dependency
  2. Update Imports
    • Replace import com.statsig.sdk.* with import com.statsig.*
  3. Update Initialization
    • Change from static methods to instance methods
    • Replace .apply {} blocks with the builder pattern
    • Replace val user = StatsigUser("user_id") with val user = StatsigUser.Builder().setUserID("user_id").build()
    • Initialize with val statsig = Statsig("key", options) and call initialize()
  4. Update User Creation
    • Use the builder pattern: val user = StatsigUser.Builder().setUserID("user_id").build()
  5. Update Method Calls
    • Replace static methods with instance methods
    • Remove Sync suffix from method names
    • Update method signatures as needed
    • Replace mapOf("key" to "value") with appropriate map creation methods
  6. Test Thoroughly
    • Verify all feature gates, experiments, and configs work as expected
    • Check that event logging is functioning correctly

New Features in Java Core

Parameter Stores

Java Core introduces Parameter Stores, which allow you to manage parameters across multiple feature gates, experiments, and dynamic configs:

Improved Performance

Java Core offers significantly better performance:
  • Faster evaluation times
  • More efficient network usage
  • Reduced CPU usage
  • Better memory management

Troubleshooting

Common Issues

  1. Missing Platform-Specific Dependency
    • Error: java.lang.UnsatisfiedLinkError: no statsig_jni in java.library.path
    • Solution: Add the correct platform-specific dependency
  2. Incompatible Method Calls
    • Error: java.lang.NoSuchMethodError
    • Solution: Update method calls to match the new API
  3. Configuration Differences
    • Issue: Features not evaluating as expected
    • Solution: Verify options are correctly configured in the new format

Need Help?

If you encounter any issues during migration, please reach out to us: