Currently, we use a single instance of ValKey for storing the token rate limit KV values. For production deployment and resilience, we need to add High Availability and sharding of the data stored.
The goal of this story is to enhance the current infrastructure for TRL and extend the configuration so that it exposes the ValKey settings.
The deliverables should include testing for edge cases, at least for UT, IT and E2E. Performance testing depends on the availability of a dedicated hardware, if not then it should be split from this issue into its own dedicated one with a test plan.
Currently, we use a single instance of ValKey for storing the token rate limit KV values. For production deployment and resilience, we need to add High Availability and sharding of the data stored.
The goal of this story is to enhance the current infrastructure for TRL and extend the configuration so that it exposes the ValKey settings.
The deliverables should include testing for edge cases, at least for UT, IT and E2E. Performance testing depends on the availability of a dedicated hardware, if not then it should be split from this issue into its own dedicated one with a test plan.