3 ms·
what is the usecase for something like this versus celery/rq ?
by sandGorgon 7y ago
what is the usecase for something like this versus celery/rq ?
- nurettin 7y agoAFAIK, celery doesn't provide a message passing bus between main process and sub-processes.
- zbentley 7y agoWell, it technically does (through its invocations of billiard, it's multiprocessing fork), but it's pretty ad hoc and not exposed for much user control. So you're basically right, I'm just being pedantic.
- nurettin 7y agoYes ok initial parameter passing and gathering results may be considered a message bus. I was going to mention that, but I got lazy.
- sandGorgon 7y agoDon't understand that clearly. Can't I put something in the queue in the main process and read it from subprocesses ?
- nurettin 7y agoIs that going to provide bi-directional communication between main and subprocesses while they are running? If it does, disregard what I wrote.
- sandGorgon 7y agoSure. You can put results in an "output" queue (which is backed by Redis) that is read by the main application. Incidentally this is how you do a notification on your UI .
- adamcharnock 7y agoHaving developed a similar library, I have written a (rough) response to this question here: https://lightbus.org/explanation/lightbus-vs-celery/ https://lightbus.org/explanation/lightbus-vs-celery/ I suspect the answer will also apply to something like Lahja.