Hi,

On our project we have been using Hazelcast for a couple of months now and
we are looking to increase usage of Hazelcast with distributed queues. I
was hoping to use Apache Camel to retrieve and process the messages in our
hazelcast cluster. (The camel route would be deployed together with the
hazelcast instance, and you would have as many camel route instances as
hazelcast cluster instances)

I had a closer look at the camel-hazelcast component. When diving into the
source code of the camel-hazelcast module I was very surprised to read the
sources of class HazelcastQueueConsumer: it is implemented as an
ItemListener.

For our clustered environment this would imply that each message would be
processed on each cluster member. Which defeats the point-to-point
messaging model. And even if the messages are processed, they remain on the
queue too.

So basically I wonder what the camel-hazelcast is meant to be used for? Can
anybody explain this implementation?

Also, is it possible to implement our scenario with camel-hazelcast?

Thanks for your help,
Benoit

Reply via email to