Apache Camel

What do you like best?

This is one of the best routing services I have ever used in my application. Apache camel is too easy to configure, code and define your end-point routes. Also you are not limited to just one endpoint routes, however you can define as much as you need as per your business requirements. The only drawback I can see is that there is no way to test without deploying the same in the application server.

What do you dislike?

It is a very low-level architecture and design. It would be nice to have a GUI to define an endpoint and test the connectivity without deploying into the server. Something like SOAP UI where you can test your SOAP API without any hustle. Also if possible drag-drop option will be very optimal and helpful for such use cases.

Recommendations to others considering the product:

If your sytem has to connect with various data points or 3rd party system where you need to exchange the data then you may give a try to Apache Camel. It is very easy to understand and implement as per business needs. I have used this product to connect with 3rd party intergration system where all the communication is via XML and it is very easy to understand and develop for enterprise level application.

What problems are you solving with the product? What benefits have you realized?

We have lots of end-points where system need to talk and pass the request to get the response. Using Apache camel it is extremely easy to configure and implement such business requirements. However, the drawback is you need someone in your team to understand and code for Apache Camel.