11 ms·

Explain, please. I'm considering using it.

• gfodor 13y ago
  When RabbitMQ breaks (and in my experience this happens), you get to ask yourself, "Which will take more time, switching queues or learning Erlang?" Usually the answer is "switching queues."
• ris 13y ago
  Operations and configuration-wise, it is _bonkers_, and massively overengineered.
  • dscrd 13y ago
    Would you agree that there's a demand for a simple and reliable MQ? Possibly one that just supports Stomp, possibly written in Golang? That just works and does nothing fancy?
    • ris 13y ago
      I've actually been using redis pubsub, which is fine for my needs and dead simple.
    • old_sound 13y ago
      It depends on what you need and what you mean by simple and reliable. RabbitMQ is used by the likes of Instagram, so not sure about what's your specific use case.
  • old_sound 13y ago
    Would you mind providing feedback to the RabbitMQ engineers? These kind of comments aren't terribly helpful to us, besides form an "I don't like it" feeling. It would be nice to see what you consider to be "massively overengineered" as well.