Hi Michal, Thanks for your response. >>> Do you need low latency? What are your SLA for avg and max response time? 100 queries/sec with max. latency of 1 sec
>>> For what perposes you plan to use Camel? To unify transport layer configuration? Do you plan to rewrite your integration architecture to direct use of database from other transport layer? If so I think Camel is a good choise to consider. The main 2 purposes of bringing in camel are as follows: - Avail advantage of the multi-transport (eg. SOAP, HTTP, TCP, JMS, File etc) support so we reduce writing transport infrastructure code - Avail the integration patterns enforced by CAMEL to ensure that data received from any transport is converted into a common object format and then sent to the business logic bean, whcih would implement the business logic in a transport-agnostic fashion (similar to the Rider Auto Parts example in Camel In Action book) Now, the question is: For the latency & traffic requirements of the product stated above, is it advantageous to use Camel for the above two purposes? Thanks MK On Fri, Aug 10, 2012 at 2:13 AM, michal.warecki [via Camel] < ml-node+s465427n571709...@n5.nabble.com> wrote: > It is about 60 msg per sec in average so it is not the problem. Like other > frameworks Camel has some overhead. Do you need low latency? What are your > SLA for avg and max response time? For what perposes you plan to use Camel? > To unify transport layer configuration? Do you plan to rewrite your > integration architecture to direct use of database from other transport > layer? If so I think Camel is a good choise to consider. > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://camel.465427.n5.nabble.com/Camel-usage-in-Online-usecases-tp5717058p5717092.html > To unsubscribe from Camel usage in Online usecases, click > here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5717058&code=bWthcnRoaWsuaGVyZUBnbWFpbC5jb218NTcxNzA1OHwtMzc4NDc0NzY2> > . > NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >
