Share throttling information between multiple instances of an app

[matbhz]

How can I share throttling information through multiple instances of an app that are managed by a load balancer?

Issue #57 answer mentions data is not persisted anywhere, therefore I can't plug a datastore (such as Redis) that would be used as a lookup store for all instances running at the same time.

I have this scenario described above in my current architecture, where 3 or more instances of the app may be running and I would like to "share" throttling information between them in order to avoid having non-deterministic 429 requests depending on which box my request hits.

[didip]

This is probably possible with Prometheus/Statsd/Graphite. I hesitate to add a database as a hard requirement.

[johan-lejdung]

@didip Would it be possible to pass your own cache though? It would not be a requirement, but would greatly help out in a distributed environment.

I'd be happy to help you explore the option.

[didip]

if you can define a sensible interfaces that works for a majority of key value, and if you can make it optional… sure, I am ok to entertain that idea.

…

On Thu, Dec 22, 2022 at 9:10 AM Johan Lejdung ***@***.***> wrote: @didip <https://github.com/didip> Would it be possible to pass your own cache though? It would not be a requirement, but would greatly help out in a distributed environment. I'd be happy to help you explore the option. — Reply to this email directly, view it on GitHub <#64 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAARZVR5FKRQGXJC7EL55MLWOSDQ3ANCNFSM4FCCO7YA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[johan-lejdung]

I'll try to have a look at the start of next year then. I think it's quite common to want to rate limit across microservices, it would be a shame if such a greatly designed library wouldn't be possible to use in those scenarios