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
I'm interested what are measures you take to disconnect bugs in your Node.js bundle from orchestration of tasks made by dependencies. Have you considered writing dependency-less master process with clear API boundary of some kind? I think master process should use just stdlib to be honest, written with help of computer aids to make it secure, with good review, while children task-running could do anything they want within their containment environment. After all this is software that runs repeating and very long-running tasks. In ideal scenario both master and client library are all dependency-less and reviewed but hey let's have some slack
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm interested what are measures you take to disconnect bugs in your Node.js bundle from orchestration of tasks made by dependencies. Have you considered writing dependency-less master process with clear API boundary of some kind? I think master process should use just stdlib to be honest, written with help of computer aids to make it secure, with good review, while children task-running could do anything they want within their containment environment. After all this is software that runs repeating and very long-running tasks. In ideal scenario both master and client library are all dependency-less and reviewed but hey let's have some slack
Beta Was this translation helpful? Give feedback.
All reactions