Skip to content

Rate limit counters are in-memory / not multi-instance safe #28

Description

@lisiur

Each instance counts independently, so behind a load balancer the effective per-subject limit is ~N × max (lib/rate-limit-store.ts).

Same single-process constraint as Jobs/Cache; an external store (Redis) or shared Postgres counter is needed before scaling horizontally.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/jobsJobs / QueuewontfixThis will not be worked on

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions