Apache Camel is an open source integration platform.
N/A
Cleo Clarify
Score 10.0 out of 10
N/A
A solution to transform EDI and non-EDI data into any format for ingestion by on-premise and cloud applications.It offers support for new variable types, and consolidated actions and conditions.
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.
CLEO Clarify is best suited in an environment where EDI is a main source of business to business electronic communications (EDI). It also is very well suited to take data from multiple sources and convert it from any to any format to fit your requirements. CLEO Clarify may be more well suited to companies that have capable IT team members such as an EDI specialist or technical people.
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.
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.
Cost wise the products may be similar but on the basis of ease of implementation and use, for us CLEO Clarify won that battle even though we hired an EDI specialist who had worked for years with Seeburger BIS. This was very telling for us as he we very well versed in Seeburger and could easily had recommended them, but instead did a thorough analysis and decided upon CLEO for our solution.
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.
CLEO Clarify has helped us take our compliance rating with our biggest customers from around 25% with our ERP integrated solution, up to 98% just by switching to CLEO and being able to onboard new customers effectively within one week where it used to take 30 to 45 days and have multiple errors.
We are able to continue to find applications that CLEO is perfectly suited for including eComm and BI data collection.
