Replies: 1 comment 1 reply
-
|
Can you elaborate a bit more on why |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In one of our application, we would need our jobs to live in the same process/environment as our app (DI, shared memeory read only ressources, database pooling, etc.)
One way to achieve that would be to trade process isolation for this convenience. It could be done through config flag.
Some of the drawbacks might be adressed :
Sidequest.restart()Performance seems the major drawback IMO as one of the purpose of a job queue is to offload the "main runloop". But AFAIK this is already indirectly the case as a child process take CPU time aswell, the risk is in non proper async code blocking the nodejs runloop.
Memory protection suffers the same problem as memory is ultimately shared between processes. The drawback here is that you would need to restart the whole app (not just sidequest) in case of memory leak.
I'm willing to work on this in case of acceptation.
Beta Was this translation helpful? Give feedback.
All reactions