Skip to content

Commit

Permalink
chore: rm beta warning about client sdks (#269)
Browse files Browse the repository at this point in the history
chore: rm beta warning about client sdks
  • Loading branch information
markphelps authored Sep 10, 2024
1 parent 745550d commit 9247f30
Showing 1 changed file with 5 additions and 12 deletions.
17 changes: 5 additions & 12 deletions integration/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ description: This document describes how to integrate Flipt in your existing app

Once you have the Flipt server up and running within your infrastructure or local development environment, the next step is to integrate the Flipt client(s) with your applications for evaluating your feature flags.

There two main ways to perform evaluation of feature flags with Flipt:
There are two main ways to evaluate feature flags with Flipt:

1. [Server-Side Evaluation](#server-side-evaluation)
1. [Client-Side Evaluation](#client-side-evaluation)
Expand All @@ -30,11 +30,11 @@ The choice of which API to use is up to you. Both APIs are fully supported and a

Flipt comes equipped with a fully functional REST API. The Flipt UI is completely backed by this same API. This means that anything that can be done in the Flipt UI can also be done via the REST API.

The Flipt REST API can also be used with any language that can make HTTP requests. This means that you don't need have to use one of our official clients to integrate your application with Flipt.
The Flipt REST API can also be used with any language that can make HTTP requests. This means you don't need to use one of our official clients to integrate your application with Flipt.

The latest version of the REST API is fully documented using the [OpenAPI v3 specification](https://github.com/flipt-io/flipt-openapi) as well as the above [API Reference](/reference/overview).

See all official REST SDKs as well as how to generate your own in the the [REST SDK](/integration/server/rest) section.
See all official REST SDKs as well as how to generate your own in the [REST SDK](/integration/server/rest) section.

### GRPC API

Expand All @@ -45,24 +45,17 @@ Since Flipt is a [GRPC](https://grpc.io/) enabled application, you can connect t
An example [Go application](https://github.com/flipt-io/flipt/tree/main/examples/basic) is available, showing how you would
integrate with Flipt using the Go GRPC client.

See all official GRPC SDKs as well as how to generate your own in the the [GRPC SDK](/integration/server/grpc) section.
In the [GRPC SDK](/integration/server/grpc) section, you can find all official GRPC SDKs and instructions for generating your own.

## Client-Side Evaluation

Client-side evaluation is another way Flipt supports evaluating feature flags. This is where your application has a local copy of the feature flag rules and evaluates them locally.

<Warning>
Our client-side SDKs are currently in **beta**.

We're actively working on improving them and adding more languages. If you have any feedback, feature or language requests, please let us know by opening an issue in our [GitHub repository](https://github.com/flipt-io/flipt-client-sdks).

</Warning>

Client-side evaluation is much more performant than server-side evaluation, but it comes with some tradeoffs. The main tradeoff is that you need to keep your feature flag rules in sync with Flipt. This means that you will need to periodically fetch the feature flag rules from Flipt and update your local copy. Our client-side SDKs provide a way to do this automatically.

Reasons for using client-side evaluation include:

- You want to reduce the number of requests your application makes to Flipt for feature flag evaluations
- You want to reduce the latency of feature flag evaluations

See all official client-side SDKs in the the [Client-Side SDKs](/integration/client) section.
See all official client-side SDKs in the [Client-Side SDKs](/integration/client) section.

0 comments on commit 9247f30

Please sign in to comment.