Hi All,

I have been evaluating Apache Camel for my Orchestration usecases. And have
realised that there are few features which are required to be built in
Camel to satisfy my requirements. I wanted to walk you through those
requirements and understand if it merges with Camel’s roadmap.

Below is the feature list we additionally require:

   1.

   Route Management: Our usecase is to cater various kinds of orchestration
   flows which needs to be executed on their trigger event. In Camel’s term we
   need capability to capture the multiple routes which can be used as a
   centralised place for managing them.
   2.

   Route Versioning: Any new change in the existing Route will be
   rolled-out in the gradual fashion, which means there will be multiple
   versions of a route which needs to be supported and executed in A/B manner.
   3.

   Data exchange control across the processor: Camel exchanges generic data
   across the processors, which can lead to change of data in unexpected
   processor boundaries. To restrict the data access boundary needs a
   type-safe way of data sharing across the processors.
   4.

   Data driven routing. Camel provides the way to route control based on
   static and dynamic across the processors. We need additional capability to
   route processors based on the data dependency.
   5.

   Mapping with Json DSL: Mapping the route definition with JSON DSL. So
   far Camel supports XML and java DSL for route definition.


Let me your thoughts on the requirements, which all make sense to be
added/extended with the Camel. We can work together to contribute.

--
Kishan Gajjar

-- 



*-----------------------------------------------------------------------------------------*


*This email and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they are 
addressed. If you have received this email in error, please notify the 
system manager. This message contains confidential information and is 
intended only for the individual named. If you are not the named addressee, 
you should not disseminate, distribute or copy this email. Please notify 
the sender immediately by email if you have received this email by mistake 
and delete this email from your system. If you are not the intended 
recipient, you are notified that disclosing, copying, distributing or 
taking any action in reliance on the contents of this information is 
strictly prohibited.*****

 ****

*Any views or opinions presented in this 
email are solely those of the author and do not necessarily represent those 
of the organization. Any information on shares, debentures or similar 
instruments, recommended product pricing, valuations and the like are for 
information purposes only. It is not meant to be an instruction or 
recommendation, as the case may be, to buy or to sell securities, products, 
services nor an offer to buy or sell securities, products or services 
unless specifically stated to be so on behalf of the Flipkart group. 
Employees of the Flipkart group of companies are expressly required not to 
make defamatory statements and not to infringe or authorise any 
infringement of copyright or any other legal right by email communications. 
Any such communication is contrary to organizational policy and outside the 
scope of the employment of the individual concerned. The organization will 
not accept any liability in respect of such communication, and the employee 
responsible will be personally liable for any damages or other liability 
arising.*****

 ****

*Our organization accepts no liability for the 
content of this email, or for the consequences of any actions taken on the 
basis of the information *provided,* unless that information is 
subsequently confirmed in writing. If you are not the intended recipient, 
you are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this information is strictly 
prohibited.*


_-----------------------------------------------------------------------------------------_

Reply via email to