camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From msnathan <>
Subject Design Question
Date Tue, 15 Nov 2011 17:05:33 GMT

  I am planning to use Camel as a Composite Service Mediator/Routing Engine.
All my back-end services/application are exposed as REST and each one of
them is running in its own jvm. I want to put Camel in front of those
services  and expose the composite service per resource/application to the

Existing Problem:

   a) Currently RIA clients call the backend service directly ( uses DNS
name/Context Path to resolve the machine ip address + load balancing)
   b) As more and more services are getting added, each service is calling
other services directly, kinda of point-to-point problem at the service

Proposed Solution:

   a) Composite service (any service calling other service directly) will be
moved from the application layer to the camel layer where we will create a
new rest service and the mediation is done between services at the Camel
   b) Non-Composite service will go thru camel (straight through processing)
to the actual service.

I am in the processing of writing a composite service for one application.
After going through the existing code, I end up having one composite service
with 8 operations on the camel front end application. Each of this operation
talks to 3 services and for each service call constructing the REST URI and
mapping the response json and aggregating them is becoming challenging. 

Is camel the right solution for the above architecture?

View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message