-
Notifications
You must be signed in to change notification settings - Fork 250
Open
Description
I have a suggestion to improve the resilience and align a bit more with industry standards.
You should not be doing clustering in your code. I adds noise and is right now preventing the script from running unclustered. There are pretty sweet tools to manage your process, bring it back up when it crashes, monitor it and finally cluster it. Tools like PM2
What I suggest is to:
- add the
pm2dependency to thepackage.json - remove the clustering logic from
app.js - change the
npm startcommand forpm2 start app.js -i maxwheremaxcan easily be changed to any number to define the number of clusters to make.
PM2 also has the advantage to be hookable for remote monitoring with almost no effort, which could be interesting for this project.
Cheers
PaulRBerg
Metadata
Metadata
Assignees
Labels
No labels