#celery

shodan45: it's a hint that even if you use redis as a result backend, you should not use it as a broker

asksol: ok... why is that?

I feel like I'm really missing something :(

...if you care about tasks executing, if task loss is not critical then redis works ok, though it's slower with the ack emulation but you can disable that for ephemeral messaging

asksol: if redis is truly that bad, then I question why celery supports it at all

is redis simply the wrong tool for the job? or is redis just flawed software?

maybe the typical workload is what I'm missing.... I need something to run jobs when the user clicks a button on a web page; this would happen at the very most 10 times a minute.

we also are (ab)using the system cron to run application-level scheduled jobs

also, going back to the user-clicks-a-button usage scenario, I need to be able to deliver a PDF/html page/image/etc. as a result

installing redis is/was relatively simple - installing rabbitmq looks quite complicated since it needs the erlang vm too