Am Montag, den 05.03.2012, 12:24 -0800 schrieb Baz: > What kind of applications would you not trust on Node.js? Should someone > like Amazon trust Node to power their shopping cart knowing that having the > one thread fail could prematurely cut off thousands of in-progress > transactions? I'm sure Node.js isn't intended to be the "fit all" solution > for everything. But are there things you would say "you should never use > Node for X, but it would be great for Y"?
Well, sure, node isn't great for everything... but you could easily mitigate lockups by having watchdogs, and a well-designed application shouldn't acknowledge that it has handled a task before all the data was written out to disk anyway. Heh, that'd be a cool project idea... a node supervisor that, when a watchdog stops responding, redirects traffic to a new worker, sends SIGUSR1 to the old one, connects to the debug port, creates a stack trace, makes a deep dump of all variables on the stack, creates a "dumpfile" and kills the old worker. I already played with deep-dumping stacktraces in the past, I have working (but slow and inefficient, it was written without too much care) code for that :)
signature.asc
Description: This is a digitally signed message part
