You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 27, 2022. It is now read-only.
@isaacs, hum... Why don't you use it anymore? Do you use something else or do you just use the built in cluster module?
It seems to me that this direction offers some things for production grade monitoring. I'll fork this look at any suggestions I can (hopefully ;) get out of you and set up some PR's...
Why don't you use it anymore? Do you use something else or do you just use the built in cluster module?
It's just easier spin up a bunch of independent VMs, and put a load balancer in front of them, especially since you usually want a CDN in front of any production site anyway. Then clusters just kind of make things confusing.
Yup... that sounds right. The cluster stuff seems more like an ops function since it provides faster recovery, fault tolerance, maybe some monitoring magic... I'll start playing around and we shall see.
Ideally, it should be that a dev-ops person could drop in something like cluster-master on top of an arbitrary application and it should just work... That's my goal anyway.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This project has not had a lot of activity. I would like to see some new features like:
exit
,online
etc..exit
in the REPL is not exactly right, I think that sock.end() is what people are looking for, update documentation/implementation.Should I make some PR's or should I fork the project and start anew?
The text was updated successfully, but these errors were encountered: