What does having Erlang experience provide for you when using RabbitMQ? Unless your rendering nodes were written in Erlang... In which case you could have easil

What does having Erlang experience provide for you when using RabbitMQ? Unless your rendering nodes were written in Erlang... In which case you could have easily just used Erlang's built in node connection primitives and used RPC's instead of the much more complicated AMQP process. I know this from personal experience. If you have a consumer based distributed worker pool, AMQP is overkill! My application is built in Erlang and the worker nodes are also built in Erlang - I initially went with using RabbitMQ to hand work out to the workers (and to receive processed results back from workers) but I quickly found it added a lot of message latency (vs. a straight RPC call) and I also had to write a lot of management code. Switching over to straight RPC was a great decision and I essentially kept the "worker queue" logic in our Python application (where it is a "solved" problem). Big topic, for sure - I should write a blog post on how my application is structured.