3 ms·
Yes, it is stable enough. BUT, that assumes you know how to write code that will work under various conditions that can and do arise. The main thing that can c
by mathrawka 13y ago
Yes, it is stable enough. BUT, that assumes you know how to write code that will work under various conditions that can and do arise.
The main thing that can cause shit to hit the fan is not properly handling errors. I highly suggest using domains, and that when an error occurs, if you can, that you gracefully exit. If not, then all other requests will just abort and that isn't very user friendly.
You will also want a way to be notified of errors, so you can stay on top of them and fix them right away. I use winston and have the error level set to email me.
If you want to talk in more detail, contact me... address is on my profile.
- masterkain 13y agoDomains are 0.10 specific I believe, and 0.10 is still bugged in few areas. I'd stay on 0.8.23 for quite some time since we are talking about stability.
- mathrawka 13y agoI'm using 0.10 in production and haven't had any bugs... what bugs are you referring to? Also domains are in 0.8
- masterkain 13y agoIs yours a large or small app? Do you use streaming/piping/remote services? Regarding bugs, there are too many to list, just see the tracker and spend some time browsing through them https://github.com/joyent/node/issues?direction=desc&page=1&sort=updated&state=open https://github.com/joyent/node/issues?direction=desc&pag... I'm fairly sure you can find pretty much anything. I'm considering removing all the npm modules from my project and go raw, since most of the obscure bugs are in the ecosystem anyway. Somehow I missed domains are also in 0.8, thanks!
- mathrawka 13y agoIt is large, but doesn't use any streaming or piping. As for remote services, just a bunch of remote APIs, and they work fine. With the changes to streams in 0.10, I can understand it having some issues. That slipped my mind... but I don't do much streaming so I just assumed it worked.