SocketCluster / SocketCluster/socketcluster
Migration socketcluster 16.2.1 to 20.0.2
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.2k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
Hello Jonathan,
We have been using SocketCluster Server (worker, broker, and state) version 16.2.1 and SocketCluster Client version 16.1.1 for four years.
Everything was working fine until now, but the worker instance is no longer working in cluster mode.
This is similar to the issue described here: https://github.com/SocketCluster/ag-simple-broker/issues/2
We previously updated the ag-simple-broker version to 5.0.0 two years ago, and it was working.
However, for the past week, the worker instance has stopped working in cluster mode, even with ag-simple-broker version 5.0.0.
We are therefore considering migrating from version 16.2.1 to version 20.0.2.
To do this, we would like to know what significant changes need to be considered for this migration.
Indeed, we can't find any documentation on this.
Thanks for your help.
stephwildcode
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 with the linked ag-simple-broker issue and compare the SocketCluster 16.2.1 and 20.0.2 migration context, focusing on worker, broker, state, and clustered mode. Done means documenting the significant migration changes and the considerations needed to move between these versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, distributed-systems, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100