[catlover76]

> it is all but impossible to run the queue in the same codebase and application server.

I am surprised, both in terms of the difficulty you faced and that you would want to; I have beef with the fact that using Celery with Django runs "worker" process on the application server by default.

[andy_ppp]

It sounds mad but because of the process isolation within the language you can trust running services within your application and message passing can be local or to a different machine in the BEAM cluster. It opens up a whole new way to think about a runtime once everything is an actor model process with a mailbox you can send messages to.

It's much better than having to worry about extra infrastructure, just deploy your app and because it's code you control you can customise what the queue is going in really bespoke and application specific ways.

[catlover76]

> to a different machine in the BEAM cluster.

Wow, that's pretty cool

[andy_ppp]

Wait until you find out you can connect an interactive shell to production and run functions in your application to debug things live…