3 ms·
I think you might find it useful to read the comments in this question on backpressure in Node.js. It points to a easy solution built into to Node's Streams. ht
by johnsonjo 11y ago
I think you might find it useful to read the comments in this question on backpressure in Node.js. It points to a easy solution built into to Node's Streams. http://stackoverflow.com/questions/25237013/node-js-unbounded-concurrency-stream-backpressure-over-tcp http://stackoverflow.com/questions/25237013/node-js-unbounde...
- rubiquity 11y agoThis article (the article we're commenting on, not the article you linked) precisely points out why Streams will not save you.
- johnsonjo 11y agoThe article we are commenting on points out that backpressure is not easily handled by the given tools of Node.js it speaks of a way to fix it from crashing from memory overload. The comment above points out in a way that I understood as Node being bad for not having a way to deal with backpressure with its own tools. The link I shared shows that Node.js does have a built in tool in streams to handle that exact problem. As other comments have said having too many connections will always eventually crash a single server. So my question is what will save you? Can it be done in the JS part of Node? Can it be done in a Node C and C++ module? I look at my self as a beginner when it comes to these things so I would surely enjoy an informative response.