SocketCluster / SocketCluster/socketcluster
Can I use SocketCluster to connect microservices?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.2k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
Hi there!
I have a system made of multiple microservices that run independently on different processes or machines. On the other side I have many devices connected to my system via SocketCluster for realtime communication. Some of those microservices have hight rate of update so I decided to publish those updates from microservices to end devices via SocketCluster channels. What I really don't know is that how can I connect those microservices to SocketCluster with a high performance connection. I prefer to avoid HTTP API on worker, because rate of updates is high and HTTP has overhead. Is it a good practice to connect Microservices to SocketCluster like a normal client? Or you suggest another options? I'm confused if I use microservices as normal clients then how can I separate my microservices from end devices so that only microservices are allowed to publish on channels.
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
No files, tests, or entry points are named. Start by reviewing SocketCluster's channel publishing and client or worker connection documentation, then establish whether microservices should connect as clients or use another supported path. Done would require a clearly documented high-performance architecture and a way to restrict publishing to trusted services.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100