*In the data ingest side, we will have around 5 million records/sec traffic*
Are you serious with your above statement? How big is that data record. Are you using Super Computing? I've never seen a system that can handle this. Regards, Jothi On Thu, Aug 9, 2012 at 12:36 PM, mk <mkarthik.h...@gmail.com> wrote: > Hi, > In our product, we have the following requirements: > 1) In the data ingest side, we will have around 5 million records/sec > traffic. These CDR records could come to us in various transports including > file, JMS, XML over HTTP etc. This data has to be received and written into > HBase > 2) In the output side, we have an online module connected to customer care > applications. Here again, we need to accept queries over various transports > like HTTP, JMS, bulk file etc. The system needs to parse the query, > implement business logic and retrieve data from HBase, send the response to > the online query. > Since the product involved a lot of transport support (like HTTP, JMS, > future expandable to TCP, UDP streams), Im considering bringing in Apache > Camel. > Does Camel suit these kind of online usecases where performance and latency > are important parameters? Does the Camel layer significantly impact > latency? > It would be very helpful if someone can: > 1) Throw some light on the performance/latency issues in Camel, if any > 2) Point to existing production examples that use Camel for similar online > usecases > 3) Point to other resources which could throw more light on this subject > Thanks & Regards > MK > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-usage-in-Online-usecases-tp5717058.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
