I understand and partially agree that AMQP is a bit complicated.
Much like XML is a complicated version of JSON.
However, I can personally vouch that this 'complexity' once somewhat mastered can be used to create messaging schemes in no time.
What's so complex about it? You have exchanges, queues, and bindings.
With a bit of practice, it's fairly simple to grasp the concepts.
"AMQP is quite unusual in that it starts low on the stack, building on protocols like TCP rather than HTTP"
This person has obviously never built anything truly high performance. Using HTTP would add a lot of latency, and he complains about message speed?
Sure 0MQ is the fastest, but with RabbitMQ you get <1ms latency.
"People who today read the AMQP specifications tend to make one main complaint: the protocol is too complex."
I wonder how many of these people actually use it.
He goes into a bunch of useless analogies but doesn't actually discuss WHAT'S complex about it.
(Usage wise, NOT implementation wise.)
A protocol doesn't HAVE to evolve. JSON being an example.
But, in the end, AMQP isn't perfect, but it can still be used to build good software.
This person knows very little about building messaging software, and he admits it himself.
I'd take his complaints with a huge grain of salt.
You can use something like protobuf to get really fast de-serialization if you really want encoding.