Hello community,
I am currently working on a feature within the Camel project that involves
processing Kafka messages (String) and performing a query based on that
message. Initially, I implemented a classic route that called a service
method responsible for executing the query. However, I encount
Yes, dividing it into chunks is a good practice. This adheres to
message-based systems in general, not specific to Camel.
Let's discuss both ways of processing messages:
1. One big message
Say the message is 100 GB+ and this is processed by some integration
software on a server, you need to scale
Following up for posterity...
The workaround I'm going with is to create a per bundle CamelContext using
Blueprint. Each module adds routes to its own context and the onException
handlers can see the appropriate Exception classes. Messages are passed to
the core application's context using the vm:
