Caching in the OpenFGA SDKs

[rhamzeh]

Checklist

• I agree to the terms within the OpenFGA Code of Conduct.

Describe the problem you'd like to have solved

FGA users can incur a latency cost. Caching at the server helps, but users still have to incur the roundtrip tax, caching at the SDK level should help alleviate these concerns and give users more control over the caching strategy

Describe the ideal solution

We would like to allow users to configure caching in the FGA SDKs - we can support an optional in-memory cache as well as an optional external redis (as a start) cache.

The cache needs to be configurable per method and per request. Users should be able to set their own rules for when to go to the cache and when to skip and what the TTL would be

Alternatives and current workarounds

No response

References

Roadmap Item: openfga/roadmap#18
Milestones: TBD

Additional context

No response