3 ms·
Yes, thanks for reminding me, NATS isnt HTTP. Didn't say AMQP is simple though. It's definitely not, but that's where the features and functionality come from.
by manigandham 11y ago
Yes, thanks for reminding me, NATS isnt HTTP.
Didn't say AMQP is simple though. It's definitely not, but that's where the features and functionality come from. It seems the issues you described are with the broker and clients, not the protocol itself, which I find to be pretty solid.
- lobster_johnson 11y agoAMQP also specifies the data model (exchanges, queues, bindings and so forth), which dictates the implementation of it. I find that data model a bit heavy-handed, but it's not terrible. However, it's not very suitable for RPC.
- nitrogen 11y agoIt's not too difficult to do RPC over AMQP by having an ephemeral reply queue per request, if your load isn't too high.