Adeptia Connect vs. Apache Camel

I recommend the program for an advanced stage, it is not a program for small companies, it is a program for medium or large companies where you know about data and its flow in which you need to make the leap to a 3.0 level of the same.I could immediately recommend it to colleagues for its great storage capacity and agile control.

Incentivized

Message brokering across different systems, with transactionality and the ability to have fine tuned control over what happens using Java (or other languages), instead of a heavy, proprietary languages. One situation that it doesn't fit very well (as far as I have experienced) is when your workflow requires significant data mapping. While possible when using Java tooling, some other visual data mapping tools in other integration frameworks are easier to work with.

Incentivized

• End users can set up pipelines within Gap to connect without having to use professional services.
• Users can simply select a particular template.
• Let's say that data integration calculates and configures a data flow very easily.

Incentivized

• open source and a great set of component feature set - always latest features available for integration
• works well with spring boot
• great community and support for any kind of workflow
• based on enterprise integration patterns which helps our developers achieve integration tasks with all kinds of API services

Incentivized

• Support only in english and not always reactive.

Incentivized

• Some of the documentation is a little sparse. In particular, its TCP-based routes use an underlying Netty server, and the interactions between Netty's decoder capabilities and Apache Camel's routing/handler capabilities can be a little muddy at times. In general it is clear which routes and endpoints are the more frequently used and which haven't been given as much attention.

Incentivized

We mainly choose Adeptia Connect for the friendly UI. From the first minutes, it was really easy to use and understand how it works and then manages complex connections.

Incentivized

Apache Camel has been the integration framework of choice, but I was not the person to make the decision to use it. Compared to other competing products like Tibco Business Works, etc., it is free and open source and its licensing policy is acceptable to the management of Cox.

Incentivized

• The user can set up the whole template and then enter the data or we simply have to connect that data by making use of connections from an account through an API.
• We can do reference lookups in the database to further enhance it before sending it to the data link and as part of this process flow
• We can attach by taking up a little bit of time or batch and this can be a multi-directional process. So I needed this data transformation

Incentivized

• Very fast time to market in that so many components are available to use immediately.
• Error handling mechanisms and patterns of practice are robust and easy to use which in turn has made our application more robust from the start, so fewer bugs.
• However, testing and debugging routes is more challenging than working is standard Java so that takes more time (less time than writing the components from scratch).
• Most people don't know Camel coming in and many junior developers find it overwhelming and are not enthusiastic to learn it. So finding people that want to develop/maintain it is a challenge.

Incentivized