Skip to main content

Different SDK Types

Overview

DevCycle has different types of SDKs, some being client-side and others being server-side. This page serves to describe the various differences between these SDK types and how to handle them. Implementation and usage change depending on which type of sdk is being used.

Client-Side SDKs

DevCycle client-side SDKs are meant for single-user contexts. This means that the SDKs have a persistent data store for the user while the SDK is being used. Evaluation of Features happen directly on the client's device. These SDKs also include the Mobile SDKs. For more information on the difference between mobile and standard client-side SDK keys, read API and SDK keys.

The current Client-Side SDKs are:

Server-Side SDKs

Server-side SDKs are used in multi-user contexts where each call to the SDK will likely be for a different user. Each call to a server SDK function requires the user's ID and any other targeting information to be past in on every function call. These SDKs are made for infrastructure, backend, and other such services.

The current Server-Side SDKs are: