Hi Pontus & Henryk, Thanks so much for very valuable ideas. They are going to be very useful for me. I need some more help from you on the following points: 1. How can I implement the state saving and reconstructing using memento in a generic way without serialization? I need to make it generic so that it can be used for this cross-cutting concern in all different type of routes. 2. This is very heavy traffic app and keeping the state in local memory is not an option as it will run out of memory as responses from services may take minutes. Also, response from services can come back to a server which does not have the state (it is in local cache of another server). I thought of using memcache (or other distributed cache). However, it does not have call-back mechanism if an entry expires. Also, it will cause problems to figure out timed-out transactions when my app is down and entries cached in memcache expires before app comes up. It makes me store state in DB. I am thinking of couchbase at this point.
Thanks, Rakesh -- View this message in context: http://camel.465427.n5.nabble.com/Event-Driven-Use-Case-tp5726809p5726927.html Sent from the Camel - Users mailing list archive at Nabble.com.
