StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POReplacing JMS with Hazelcast?
text
Body
copied!<p>We are currently running a distributed Java application connected by a set of JMS queues (no topics). The Java application makes heavy use of the Apache Camel framework, which is also used to communicate via JMS. As JMS provider we have ActiveMQ in use. Our requirements on the queuing solution are quite basic in terms of features - somehow comparable to local Java queues and Camel SEDA queues:</p> <ol> <li>The queues need to be highly available</li> <li>In average the message is quite small (several KB), but there must not be a restriction on the size (i.e., a small percentage of the messages transferred have several MBs)</li> <li>Delivery must be "exactly once" (Amazon SQS, for example, guarantees "at least once" only, which is not acceptable for us)</li> </ol> <p>We do not require persistent queues, since messages are stored in a database before entering the queuing system. So far, ActiveMQ is working quite well for us after spending some time on the setup. However, there are two issues because of which we are searching for a different solution:</p> <ul> <li>We currently achieve high-availability by running AMQ in JDBC Master-Slave-Mode. Failovers work quite ok, but not as transparent as desired.</li> <li>The JDBC store has a negative impact on performance, especially if we transfer larger messages (>= 2-3 MBs) over several (> 6) queues. Furthermore, we have the feeling to unnecessarily bother our database.</li> </ul> <p>We know that AMQ supports HA using Zookeeper since version 5.9. Some time ago, however, we started to consider/evaluate Hazelcast as a replacement for AMQ. So long, Hazelcast looks quite charming, since it seems to fulfill all of our requirements and seems to be much simpler to run than AMQ with Zookeeper. Furthermore, Camel provides nice support for using Hazelcast as queuing solution via its Hazelcast SEDA features. Given the fact that Hazelcast seems to be the perfect replacement for AMQ for us, we somehow wonder that there is not much information available on the Web discussing Hazelcast as a (serious) replacement for JMS. Thus, we would like to know:</p> <ul> <li>Are there any drawbacks from replacing JMS with Hazelcast (performance, reliability,...)?</li> <li>Has anyone experienced problems with multi-MB messages in Hazelcast?</li> <li>Has anyone experienced any reliability issues with Hazelcast? We are still using 2.6 at the moment (because the Camel component is currently using that version) and have <a href="http://cr.yp.to/daemontools.html" rel="nofollow">daemonized</a> it on Ubuntu. So far it seems to be running flawlessly, but some additional experiences would be nice to hear.</li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload