RabbitMQ has been a useful stop-gap in development and it helped us quickly throw together a service-oriented architecture.
It wasn't without problems though. The command-response over the same exchange as the pub-sub meant that anyone could listen to commands. Any number of processes could respond to a given service name, which leads to unpredictable results. There's no way of knowing if a process is running for a given service, or if your commands are ready to be received. On top of that, the Erlang processes of RabbitMQ added a large start-up penalty on the Pis when booting up.
RabbitMQ has been a useful stop-gap in development and it helped us quickly throw together a service-oriented architecture.
It wasn't without problems though. The command-response over the same exchange as the pub-sub meant that anyone could listen to commands. Any number of processes could respond to a given service name, which leads to unpredictable results. There's no way of knowing if a process is running for a given service, or if your commands are ready to be received. On top of that, the Erlang processes of RabbitMQ added a large start-up penalty on the Pis when booting up.
The new broker attempts to solve these issues.