[Task]: Provide User/Gateway wise different websocket connection limits
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Please select the area the issue is related to
Area/Management (Management API or Management Portal UI)
Please select the aspect the issue is related to
Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)
Description
Currently all the gateways are ratelimited from over provisioning connections based on global limit. But when different organizations are served from a single platform-api we need to rate limit separately.
- We can bring in different categories and apply different limits. That would be a simple solution. (Ex. Free, Tier1, Tier2 etc)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the existing global gateway WebSocket connection rate limit in the platform API, then determine how user, gateway, organization, or category limits should be represented. Done means separate limits can be applied for the organizations served by one platform API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100