Absolutely, I'm working on an MMO, and the complexity/flexibility of the AMQP protocol has been a god send.
However, I do agree that its concepts are somewhat convoluted for a new user, it took me quite a bit of digging to get the basics of what an exchange/queue was and what bindings mean, etc.
However, 0MQ looks attractive but simply doesn't have what's needed for a complex project that spans languages, platforms, and usages beyond the basic pub-sub.
I would compare both protocols as XML vs. JSON, whereas XML may be tedious but it's absolutely necessary for some cases, specially where tight specifications are needed.
However, I do agree that its concepts are somewhat convoluted for a new user, it took me quite a bit of digging to get the basics of what an exchange/queue was and what bindings mean, etc.
However, 0MQ looks attractive but simply doesn't have what's needed for a complex project that spans languages, platforms, and usages beyond the basic pub-sub.
I would compare both protocols as XML vs. JSON, whereas XML may be tedious but it's absolutely necessary for some cases, specially where tight specifications are needed.