The better option for this is a serverless or worker architecture. Take a look at this article, https://hackernoon.com/a-crash-course-on-serverless-with-node-js-632b37d58b44 for some starting points. You build process could pull in the latest javascript or have a default script that pulls in the code to run. This situation is not always best, as it could lead to unknown code running if the process were to be compromised or hacked.
On Thursday, May 9, 2019 at 2:18:55 AM UTC-5, Pradeep Das wrote: > > We would like to run a NodeJS docker container, which would execute some > isolated arbitrary JavaScript function and then kill the vm. Also the > source code of the JavaScript has to be obtained from a remote location. > Would we be able to do rate limiting on it - if so, what are the options > available - time, i/o, etc...? > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. To post to this group, send email to nodejs@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/e1e37668-7833-4972-bf9e-7e7a85eea88e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
