Hi, as far as I understood , child_process.spawn() would be enough for high-level arch (image) , but if that's include e.g. back-end CPU heavy computations we should either fork() or even use a cluster_module which exploits fork under the hood : with forking we can spawn new process but with a new V8 context making it multi-threaded like (image) . When I said multi-threaded , I meant concurrent cooperative multitasking as what Node.js nature is like , of course without getting into greater detail tho ...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi, as far as I understood , child_process.spawn() would be enough for high-level arch (image) , but if that's include e.g. back-end CPU heavy computations we should either fork() or even use a cluster_module which exploits fork under the hood : with forking we can spawn new process but with a new V8 context making it multi-threaded like (image) . When I said multi-threaded , I meant concurrent cooperative multitasking as what Node.js nature is like , of course without getting into greater detail tho ...