Harness Feature Flags support client-side and server-side SDKs for a number of programming languages.
Supported client-side SDKs
The following table lists the client-side Feature Flag SDKs that Harness supports.
Supported server-side SDKs
The following table lists the server-side Feature Flag SDKs that Harness supports.
|.NET||.NET SDK Reference|
|Go||Go SDK Reference|
|Java||Java SDK Reference|
|Node.js||Node.js SDK Reference|
|Python||Python SDK Reference|
|Ruby||Ruby SDK Reference|
|Apex||Apex SDK Reference|
|Erlang||Erlang SDK Reference|
|PHP||PHP SDK Reference|
The Relay Proxy, which allows for offline and hybrid Feature Flags usage, is provided as a Docker image and can be used in any environment where the Docker image can be run. The Relay Proxy can be enhanced with Redis as a cache in environments where this is possible.
Hybrid and offline usage
Harness Feature Flags allows for both completely offline usage as well as hybrid usage via the relay proxy. Hybrid usage can be in the form of:
- The application is online and only talks to the Relay Proxy, while the Relay Proxy has connectivity to Harness.
- The Relay Proxy is bundled with the application at build-time with a working configuration file, and neither the application nor the Relay Proxy have connectivity to Harness.
There are no limitations for using Feature Flags in any cloud or non-cloud environment as long as the languages needed are supported with an SDK, and connectivity to either Harness or the Relay Proxy can be established.
For information about what's supported for other Harness modules and the Harness Platform overall, go to Supported platforms and technologies.