camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Preben.Asmussen" <p...@dr.dk>
Subject Re: Using Camel in large project (300 Applications to integrate)
Date Thu, 17 Sep 2015 06:57:53 GMT
Hi Nick

The reason we typically have 2 war files pr integration is to separate the
responsibilities between provider and consumer systems. 
An example :
Recieve xml files in a folder -> transform them -> send the message to 1 or
more consumer systems.

Camel context 1 (in war file1) -> reads the xml and transforms it and puts
in on a jms queue -> myqueue.
Camel context 2 (in war file2) -> dequeues from myqueue and sends payload to
consumer systems.

The benefit is that you can deploy/scale them separately even on different
nodes, and there is no coupling between provider and consumer systems (via
jms queue) so systems can come and go without affecting each other.

Best,
Preben




--
View this message in context: http://camel.465427.n5.nabble.com/Using-Camel-in-large-project-300-Applications-to-integrate-tp5771540p5771576.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message