I'm trying to find documentation on how the queue system works, and what parts of craft relies on it. To my current understanding, the queue is normally executed when users are logged in to admin, and search indexes are updated via queue?
Also, I use webhooks, which seems to be executed the same way.
Publishing pending posts though, doesn't seem to use the queue?
I don't have any
queue/listen task running, but since I'm running a dockerized version I could run a parallel container which just invokes
craft queue/listen if needed, would that be favorable, and then I would disable the
runQueueAutomatically setting I assume?
Since I'm also running this in AWS, I have the option to run the queue via SQS, what would be the benefits of that? I assume the default queue is just stored in the database, but I assume it is doing some sort of locking to prevent multiple executions, if I would have multiple queue daemons running. So only real benefit would then be, that the information isn't stored in database (thus, not part of backups for instance), because the load on the database seems abysmal for any normal scenario.