4 ms·
Don't throw out ActiveMQ if you want a lightweight solution -- just use it's STOMP support. STOMP is great, it is "enterprise compliant", but lightweight and v
by aaronblohowiak 16y ago
Don't throw out ActiveMQ if you want a lightweight solution -- just use it's STOMP support. STOMP is great, it is "enterprise compliant", but lightweight and very easy to understand. I am also a fan of redis and its pub/sub features, but using STOMP on ActiveMQ will let the complexity of your messaging infrastructure grow along with your needs. Evetually need persistence? flip a switch. Need a CBR or other ESB features? Start turning them on.
- sandGorgon 16y agoseconded. I think every messaging broker needs to support the STOMP protocol now. It is cross-language and a whole lot of products are being built around the protocol, including some that wean you away from JMS (e.g.HornetQ, previously known as JBoss Messaging Server)
- aaronblohowiak 16y agoShould be noted that there are also ruby and node.js STOMP clients