cagdas: i'm not i understand your problem correctly, but, the multiplier doesn't look like a problem here to me
*i'm not sure
ezekielnoob2 has quit
kaakku joined the channel
hell_razer joined the channel
hell_razer has quit
cagdas has quit
hell_razer joined the channel
domino14 joined the channel
hell_razer has quit
domino14 has quit
altipard joined the channel
hell_razer joined the channel
altipard has quit
hell_razer has quit
jessepollak has quit
Frosh joined the channel
ezekielnoob joined the channel
ezekielnoob2 joined the channel
ezekielnoob has quit
hell_razer joined the channel
hell_razer has quit
hell_razer joined the channel
hell_razer has quit
kaakku has quit
Flonka joined the channel
harlowja is now known as harlowja_away
SoftwareMaven has quit
Guest55665 joined the channel
atomekk joined the channel
Guest55665
Have a scenario for a company with 5 facilities and each one with a broker. Does Celery allow routing between brokers?
Guest55665 is now known as Patrick99
hell_razer joined the channel
Patrick99 is now known as patw33
patw33 is now known as Patrick99
malinoff
Patrick99, you can create multiple Celery instances, for each broker. Answering your question: no, using a single Celery instance it is not allowed
kaakku joined the channel
Patrick99
The thing is that a client can't directly connect to a broker from another branch
so they would have to submit it to the local queue and then it would have to routed from a specific worker to the other broker
malinoff
Patrick99, i think you should not think about celery possibilities on that level, but about broker availabilities. For example, rabbitmq can do that: https://www.rabbitmq.com/distributed.html
Patrick99
i know was just attached to the ease of deployment of Redis as it can just run as another service on one of our servers
so i was hopeing to make it work with Redis
seems like for rabbitmq i would need another virtual machine per branch