The transactional enqueue issue is exactly what makes me unsure about the callback model.
With in-app queues you get the nice property that the job can be created in the same DB transaction, which is harder to keep once the runner lives outside the app.
I'm trying to understand if the simplicity of an external runner is worth that trade-off for smaller apps.
With in-app queues you get the nice property that the job can be created in the same DB transaction, which is harder to keep once the runner lives outside the app.
I'm trying to understand if the simplicity of an external runner is worth that trade-off for smaller apps.