khemssharma / khemssharma/Chess
WebSocket connections should be offloaded (in form of a microservice) from the main server (scalability issue)
Open
Nobody has claimed this yet.
architecture
backend
good first issue
needs-design
performance
- Dominant language
- TypeScript
- Stars
- 29
- Forks
- 2
- Avg merge
- 2m
- Merged PRs (30d)
- 5
Description
Heavy traffic or a thousand of WebSocket connections can be offloaded from the main server into a separated microservice that can scale.
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 server's WebSocket handling and documenting how connections and traffic are currently managed; done would mean a defined, scalable microservice arrangement that offloads WebSocket connections from the main server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100