SocketCluster / SocketCluster/socketcluster
Try communicating with brokers via default Node.js IPC instead of ncom (maybe)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.2k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
The ncom module was introduced into socketcluster and sc-broker before Node.js made it possible to pass socket handlers between different processes. Now that it is possible, consider switching to Node.js IPC instead of ncom (ncom uses UNIX domain sockets in Linux and named pipes in Windows).
Consider if an IPC solution is capable of dealing with and recovering from process failures.
The IPC handle for the broker server will need to be passed to both the SC master process AND to each worker
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
Start by examining how ncom is used in socketcluster and sc-broker, then review Node.js IPC handle passing between the SC master process and workers. Investigate whether the IPC approach recovers from process failures and supports the broker server handle for all required processes. Done means a justified migration plan or implementation that preserves broker communication and failure recovery.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100