I'm sure this question has been asked before, but I've seen a lot of message queue implementations out there, and RabbitMQ seems quite new. Is there some overriding architectural paradigm that sets it apart from competitors? Is it the details in the APIs that make it clear and simple to use, or is it remarkable reconfigurability that sets it apart?
I'm going to make a point of giving RabbitMQ a trial in a semi-experimental project I've just started, and going to create a queuing requirement just for it, but I have only a vague notion of all the different types of queuing requirement types out in the real world, and whether RabbitMQ can satisfy most of them, or a certain subset.
The short version of my question is thus just, why RabbitMQ?