allisonsdad wrote:
> 
> .. My goal is to have unique services...

Well, Bret, by wanting to use unique services, you fall down to the JBI
clustering again. We started like that too, until we changed the vision on
how to do the thing completely. It may not be possible to do in your case.

Actually, we use queues as the clustering points. So, taking the following
example of a camel route:


queue1 -> MockPointA -> MockPointB -> queue2 -> MockPointC -> MockPointD ->
MockPointE -> queue3

Now, considering that "MockPointx" are the services you want to run over the
message you're passing on your system, you'd write that message on queue1,
and pass through the camel route until you reach queue3.

Now, the clustering we use is, we put ALL services available in ALL
instances of karaf. The routes in each of those karaf instances would be:

from(queue1).to(MockPointA).to(MockPointB).to(queue2)
from(queue2).to(MockPointC).to(MockPointD).to(MockPointE).to(queue3)

Now we implement a network of brokers (let's say, 5 brokers) which work
together and are aware of the existance of 5 karafs that can execute all the
points. By passing the message from MockPointB to queue2, you're actually
delegating the choosing of the next karaf instance to be called to the
ActiveMQ broker. So, the message may have started on MockPointA of instance
karaf1 (for example), and will execute MockPointB on karaf1 too, but on
reaching queue2, it may continue on karaf1 or (based on balancing rules you
setup) find out that it is, after all, better to switch to karaf2 (or 3 or 4
or 5) which may be idle waiting for messages to process. Each time you
introduce a queue between points, you actually give the chance of the
message to "jump" between karafs.

It works well on our case, but as I said, if you need specific instances to
do only one job, then you will not profit much from this approach.
-- 
View this message in context: 
http://old.nabble.com/Servicemix-4.2-clustering-issues.-tp28729394p28804589.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to