SDK Latency

The Hackle SDK uses stored configuration to process A/B Test, Feature Flag, and Remote Config distribution locally. No network call is made during the distribution process.

• The SDK fetches configuration from the Hackle server during initialization.

• Events are stored internally and then sent asynchronously in batches at regular intervals.

• The track() call itself does not make a network call.

Client and Server SDKs are designed to match the characteristics of their respective environments, and there are minor differences in how they behave accordingly.

Client-side SDK

1. During SDK initialization, configuration data set in the Dashboard is fetched and stored in the SDK. You can also fetch it periodically or on demand.

2. When calling A/B tests, Feature Flags, or Remote Config, the operation is processed using only the configuration data stored inside the SDK, with no network call. When calling event tracking, events are not sent to the server immediately but are only stored in internal storage.

3. Collected events are periodically sent to the Hackle server asynchronously via background tasks. When the app closes or the website is navigated away from, any remaining events are sent to the Hackle server.

Server-side SDK

1. During SDK initialization, configuration data set in the Dashboard is fetched and stored in the SDK. The latest configuration data is then fetched every 10 seconds.

2. When calling A/B tests, Feature Flags, or Remote Config, the operation is processed using only the configuration data stored inside the SDK, with no network call. When calling event tracking, events are not sent to the server immediately but are only stored in internal storage.

3. Collected events are periodically sent to the Hackle server asynchronously via background tasks.