Is RabbitMQ practical for RPC-esque bidirectional use during request processing?

Question

Super simple question, I couldn't find a concrete answer out there.

Is RabbitMQ suitable for RPC-like operations when processing HTTP requests?

I'm interested in firing off a message when a user HTTP request is received, waiting for the response from a backend server, and then sending the response to the client.

Is that a common use scenario? Are people doing it with success? Any pitfalls? Any examples or common design patterns?

Possible duplicate: http://stackoverflow.com/questions/9381909/synchronous-amqp-from-php/9404566 — Brian Kelly, Mar 13 '12 at 14:41

score 2 · Accepted Answer · answered Mar 20 '12 at 20:36

2

Yes we use rabbitmq in a similar fashion in production.

See Request Reply Pattern

answered Mar 20 '12 at 20:36

LenW

3,054
1
24
25

Well I guess you can't argue with use in production! Thanks! – Andrew Mar 21 '12 at 14:07
We looked all over for a simple way to expose amqp over http, its not a straight forward mapping. If was starting today I would do it with node.js (node-amqp) and build the http protocol the way i wanted to support my particular use cases. The biggest thing to think about is authentication via http to rabbit .. – LenW Mar 21 '12 at 19:15

score 1 · Answer 2 · answered Mar 20 '12 at 20:44

1

This has worked for me, I do suggest you look at the Web messaging extentions/tools though:

http://www.rabbitmq.com/devtools.html#web-messaging

answered Mar 20 '12 at 20:44

dgorissen

6,207
3
43
52

Is RabbitMQ practical for RPC-esque bidirectional use during request processing?

2 Answers2