On Mon, Jun 4, 2018 at 8:30 AM, Jeremy Cline <jeremy(a)jcline.org> wrote:
I had a hard time justifying choosing STOMP over AMQP because most
brokers just map the other protocol they focus on onto STOMP. It's true
the the spec is short, but it leaves a lot up to individual
implementations as far as I can tell (like how topic matching works, for
example).
It's nice to give the flexibility to clients by exposing both. I
haven't seen a problem with topic matching in my experience so far.
One thing I found with AMQP vs STOMP is that it's possible for AMQP
clients to (accidentally) emit "binary" message bodies, and then
ActiveMQ does not translate or expose these as plaintext JSON for
STOMP clients. It just looks like an empty message body to STOMP
clients, or possibly garbage. The solution was for clients to
translate the messages to text/json prior to sending. (Of course if
you never enable STOMP on your broker at all, maybe this won't be a
problem :)
- Ken