SocketCluster / SocketCluster/socketcluster
[Question] ca scc-brokers run locally
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.2k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
To connect between scc-cluster we need scc-state and scc-brokers right? I have deployed a scc-state and scc-brokers in a public ip and it works. But if the scc-state is in a public network and scc-brokers are in local network(same network with ssc-cluster), scc-clusters cannot connect to each others. Can any one tell me why? Because I have an ideal of connect all scc-clusters without a centralized server. I mean each scc-cluster will connect to a local scc-broker, scc-state just make the connection between sc-brokers. So that, the data can be transformed between them. Is that possible with this project? Thanks
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
The issue mentions scc-state, scc-brokers, and scc-clusters but names no files, tests, or entry points. Start by tracing the documented connection and deployment flow for these components, then determine whether the proposed local-broker topology is supported. Done should clearly document the supported topology or identify the configuration and networking change required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- backend, distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100