[sandGorgon]

what is the usecase for something like this versus celery/rq ?

[adamcharnock]

Having developed a similar library, I have written a (rough) response to this question here: https://lightbus.org/explanation/lightbus-vs-celery/

I suspect the answer will also apply to something like Lahja.

[nurettin]

AFAIK, celery doesn't provide a message passing bus between main process and sub-processes.

[zbentley]

Well, 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]

Yes ok initial parameter passing and gathering results may be considered a message bus. I was going to mention that, but I got lazy.

[sandGorgon]

Don't understand that clearly. Can't I put something in the queue in the main process and read it from subprocesses ?

[nurettin]

Is that going to provide bi-directional communication between main and subprocesses while they are running? If it does, disregard what I wrote.

[sandGorgon]

Sure. 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 .