Apache Camel vs. Cloudera Manager

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

Cloudera Manager is well suited for environments and deployments where the administrator user base is not well versed in the Apache Hadoop ecosystem or the Linux command line interface.

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

• Cloudera Manager has an easy to use web GUI. You can start and stop cluster and services. It will start and stop services in a cluster in the right order. You can monitor the cluster, services, and physical host hardware as well.
• Cloudera Manager has an easy to use API that allows us to create scripts to automate deployment process.
• Cloudera Manager has an option to add additional services that you could manage via the web GUI.

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

• Support for third-party Python APIs within Cloudera Manager extension framework
• Providing more reporting/logging functionality as part of the open source distribution
• Support for the latest RHEL versions sooner in the release lifecycle

Incentivized

It meets all my customer's needs.

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

I have not used any competitors, such as Hortonworks, because Cloudera Manager just works and meets all my customer's needs. I only have deployed Hadoop using command line, which is not easy to use and manage.

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

• Cloudera Manager has allowed our organization to deploy Apache Hadoop to operations quicker and with less training versus using the command line exclusively.
• Increased employee efficiency.
• Increased product adoption.

Incentivized