Creating a NewSdkClient

[keitherw]

Hi,

Is it better to save the client that was created via the client.NewSdkClient for subsequent operations or is it better to simple obtain a new client for each request.

Also, we've noticed during stress tests (8.1.4 version) that openFGA was having issues with running out of Postgres connections, is there a known issue concerning that?

And periodically, the listObjects would fail (logs didn't seem to match the postgres issues) so I was wondering if there is a time limit for the client that we obtain?

[rhamzeh]

Hi @keitherw

Is it better to save the client that was created via the client.NewSdkClient for subsequent operations or is it better to simple obtain a new client for each request.

We very - very - strongly recommended to use the client, especially if you are using client credentials. It will handle the connections for you as well as caching the token and refreshing it when needed. If you were to generate a new client, you would incur the latency (an performance) cost of:

1. Not sharing the http connection pool across requests
2. Having to request a new token on every request

If for some reason you cannot share the SDK Client, we recommend you do the token handling refresh externally, and pass the API Token to the SDK. Also, some SDKs let you pass in the underlying HTTP library so that you can share the connection pool across multiple SDK initializations.

Also, we've noticed during stress tests (8.1.4 version) that openFGA was having issues with running out of Postgres connections, is there a known issue concerning that?

Have you taken a look at: https://openfga.dev/docs/getting-started/running-in-production#database-recommendations ?

And periodically, the listObjects would fail (logs didn't seem to match the postgres issues) so I was wondering if there is a time limit for the client that we obtain?

Take a look at: https://openfga.dev/docs/interacting/relationship-queries#caveats