Alchemy Micro-Service Framework: Using RabbitMQ Instead of HTTP

Re:Alchemy Micro-Service Framework: Using RabbitMQ Instead o... by manigandham on Monday March 14, 2016 @09:08PM (#11286790)

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.

[ Parent | on HN ]

Re:Alchemy Micro-Service Framework: Using RabbitMQ Instead o... by lobster_johnson on Monday March 14, 2016 @09:43PM (#11286916)

AMQP 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.

[ Parent | on HN ]

Re:Alchemy Micro-Service Framework: Using RabbitMQ Instead o... by nitrogen on Tuesday March 15, 2016 @03:34AM (#11288062)

It's not too difficult to do RPC over AMQP by having an ephemeral reply queue per request, if your load isn't too high.

[ Parent | on HN ]