Monday 25 February 2019

Is using a module like concurrently to run processes in production a bad practice?

I am deploying a number of worker processes that will be doing backend processing work but not doing any sort of web serving or scaling. They are all super lightweight so I don't want to deploy each worker to its own instance and unfortunately I'm not super well versed with docker. The path forward to me looks like I could simply use something like concurrently to launch each worker process and then call it a day, but I'm not sure if that module is just meant to be used for local development. Thanks!

Submitted February 26, 2019 at 03:31AM by bch8

No comments:

Post a Comment