Thoughts about ESB, EIP and Camel
In the open source ESB world, Camel is more and more popular to implement orchestrations based on EIPs.
I wonder why such an interest for Camel. Nothing could be further from my mind than to challenge Camel, but I wonder about growing request about implementing service with the programming language 'Camel' when it seems to me that the business world requires more and more development efficiency.
The development efficiency is often linked to graphic editors through drag & drop features instead of writing source code.
In PetalsLink [1], editor of Petals ESB [2], we give priority to the user instead of the experienced developer. That's why, we are working on a graphic editor inside Petals Studio to implement orchestration based on EIPs. This editor is responsible to export the orchestration for our existing EIP service engine or a futur Camel service engine. [1] http://www.petalslink.com
[2] http://petals.ow2.org
I wonder why such an interest for Camel. Nothing could be further from my mind than to challenge Camel, but I wonder about growing request about implementing service with the programming language 'Camel' when it seems to me that the business world requires more and more development efficiency.
The development efficiency is often linked to graphic editors through drag & drop features instead of writing source code.
In PetalsLink [1], editor of Petals ESB [2], we give priority to the user instead of the experienced developer. That's why, we are working on a graphic editor inside Petals Studio to implement orchestration based on EIPs. This editor is responsible to export the orchestration for our existing EIP service engine or a futur Camel service engine. [1] http://www.petalslink.com
[2] http://petals.ow2.org
| -- Christophe DENEUX CTO PetalsLink |