Apache Camel Processor Purpose

Question

New to Apache Camel and just wondering ... if I'm building an image processing application that does some long running image processing jobs on very large image files, is an Apache Camel "Processor" the "best place" for this code ? The processing may take up to 15 minutes.

http://camel.apache.org/processor.html

Cheers !

score 2 · Accepted Answer · answered Dec 14 '13 at 17:24

2

the Processor interface just provides a way to call custom Java code from a route, it can be used for anything really...you can also use Bean integration to simply call your existing POJO code w/o any changes, etc.

as for your long running process...you should run this asynchronously and setup a consumer to pickup the results when they are ready, (file consumer, etc).

answered Dec 14 '13 at 17:24

Ben ODay

20,784
9
45
68

There is no should use async for long running, if processing 15 min is fine sync then do that. Its whether the caller can wait that long or not (if a caller is there to expect a reply). Use cases with no callers, like from file -> process (15 min) -> to ftp, can be perfect fine. – Claus Ibsen Dec 15 '13 at 12:26

score 0 · Answer 2 · answered Sep 17 '19 at 07:30

As Ben ODay says, Processor - is the way you are able to apply your code to transform/process the message (read - data). Therefore it is the right place for your task. Bean integration and Processor - it's about how you provide your code for Camel. Actually they are the same things. How about long time of processing - you should be worred if you produce a large count of messages into the route. What kind of queue do you use? And what count of messages do you produce? You should read about Seda component and its option named "concurrentConsumers". You could manage concurrent processing by using this option as well.

Apache Camel Processor Purpose

2 Answers2