What's supported in Harness FME

This topic lists platform and technologies supported by Harness Feature Management & Experimentation (FME).

For more information about FME features and functionality, go to the Harness FME overview.

For information about upcoming and recently released features, go to the Harness FME product roadmap.

For information about what's supported for other Harness modules and the Harness Platform overall, go to Supported platforms and technologies.

Supported server-side SDKs

The following table lists the server-side FME SDKs that Harness supports.

SDK	Documentation
Go	Go SDK reference
Elixir Thin Client	Elixir Thin Client SDK reference
Java	Java SDK reference
.NET	.NET SDK Reference
Node.js	Node.js SDK Reference
PHP	PHP SDK reference
PHP Thin Client	PHP Thin Client SDK reference
Python	Python SDK reference
Ruby	Ruby SDK reference

Supported client-side SDKs

The following table lists the client-side FME SDKs that Harness supports.

SDK	Documentation
Android	Android SDK reference
Angular utilities	Angular utilities reference
JavaScript Browser	JavaScript Browser SDK Reference
Flutter plugin	Flutter plugin Reference
iOS	iOS SDK reference
Javascript	Javascript SDK reference
React	React SDK reference
React Native	React Native SDK reference
Redux	Redux SDK reference

Supported RUM Agents and SDK Suites

RUM Agents collect Real User Monitoring events and send these events to Harness. Harness FME also supports FME SDK Suites that include RUM Agents. The following table lists the FME RUM Agents and FME SDK Suites that Harness supports.

FME SDK Suite	FME SDK Suite documentation	RUM Agent documentation
Android	Android SDK Suite reference	Android RUM Agent reference
iOS	iOS SDK Suite reference	iOS RUM Agent reference
JavaScript Browser	JavaScript Browser SDK Suite Reference	JavaScript Browser RUM Agent reference

Split Evaluator

For languages where there is no native SDK support, Harness offers the Split Evaluator, a small service capable of evaluating some or all available FME features for a given customer via a REST endpoint.

Split Synchronizer

The Split Synchronizer service is built for languages that do not have a native capability to keep a shared local cache, which is needed to evaluate FME feature flags.

This tool coordinates the sending and receiving of data to a remote datastore that all of your processes can share. Out of the box, Split Synchronizer supports Redis as a remote datastore. The Synchronizer service runs as a standalone process in dedicated or shared servers and it does not affect the performance of your code or FME SDKs.

Split Proxy

The Split Proxy enables you to deploy a service in your own infrastructure that behaves like Harness servers and is used by both server-side and client-side SDKs to synchronize the flags without connecting to Harness FME's actual backend directly.

This tool reduces connection latencies from the SDKs to the Harness servers transparently, and when a single connection is required from a private network to the outside for security reasons.

Running in the cloud

There are no limitations for using FME 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 Split 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.

What else does Harness support?

For information about what's supported for other Harness modules and the Harness Software Delivery Platform overall, go to Supported platforms and technologies.