Re: Camel use case with Akka

2014-10-29 Thread gmh
websocket and each json received will have to be operated on in an atomic fashion (single unit of work). Gordon -- View this message in context: http://camel.465427.n5.nabble.com/Camel-use-case-with-Akka-tp5758237p5758300.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel use case with Akka

2014-10-28 Thread Andreas Gies
readed(?) that we will not be > able to process a huge amount of data in a timely fashion. > What have your experiences been? > Is Akka a good choice? Any other options? > Gordon > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-us

Re: Camel use case with Akka

2014-10-28 Thread Henryk Konsek
Hi Gordon, > Subscribe to websocket queue and retrieve json from the queue > process each json thru Camel routes (atomically) > assume large amount of data You can achieve it with Camel alone or with Camel as the endpoint point [1] delegating processing to the Akka. > What would the appropriate

Camel use case with Akka

2014-10-28 Thread gmh
/Camel-use-case-with-Akka-tp5758237.html Sent from the Camel - Users mailing list archive at Nabble.com.