title: Is RabbitMQ practical for RPC-esque bidirectional use during request processing?
body: <p>Super simple question, I couldn't find a concrete answer out there.</p>
  
  <p>Is RabbitMQ suitable for RPC-like operations when processing HTTP requests?</p>
  
  <p>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.</p>
  
  <p>Is that a common use scenario? Are people doing it with success? Any pitfalls? Any examples or common design patterns?</p>