Apache Camel is an open source integration platform.
N/A
Jitterbit
Score 7.0 out of 10
N/A
Jitterbit is a cloud integration technology for cloud, social or mobile apps. It provides accessibility for
non-technical users, including easily creating API’s and data transformation scripts within the
integrations.
$100
Starting Price Per Month
Pricing
Apache Camel
Jitterbit
Editions & Modules
No answers on this topic
Jitterbit
$100.00
Starting Price Per Month
Offerings
Pricing Offerings
Apache Camel
Jitterbit
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Apache Camel
Jitterbit
Features
Apache Camel
Jitterbit
Cloud Data Integration
Comparison of Cloud Data Integration features of Product A and Product B
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.
Small to medium sized companies are great prospects for this product. It's pretty easy to set up, learn and maintain. You can scale it too, so start with an easy integration, learn the ropes and expand your usage. If you have fairly simply needs for a handful of fields and just one or two external systems to feed into Salesforce, this is the go-to product. If you're a larger company needing more complex integrations where extremely high reliability is needed and any downtime means revenue loss, you probably already have a different product in mind. Then again, you probably have an entire team that handles integrations and a data warehouse to support it!
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.
Some of the more advanced transformation possibilities aren't exactly clear without a lot of digging. Very basic connections (e.g. map this field to this field) along with basic transformation scripts (e.g. multiply X * Y) are super easy. But I know there are a ton more features and functionality that I feel is somewhat buried in the product
I have been evaluating other tools as a continuous improvement practice. I would like something that would be easier to use for a non-technical user. I work for a small organization and have no back-up for Jitterbit if something happens to me. We don't have the technically savvy employees to understand it.
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.
Hands down, Jitterbit is more cost-effective than Informatica, either on-prem or cloud and the value only goes up from there. Reusability and ease of creation make in-house training simple and the end result is we leverage Jitterbit for much more than what we initially considered it for. Having used Oracle and TIBCO before as well, I find they are the tools of yesterday, not able to keep up in terms of functionality or price. Mulesoft would be a more relevant comparison, and I feel we lean on Mule far more than Jitterbit, but both tools have their place and their strengths (and weaknesses!).
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.
We moved from a product that was failing regularly (jobs were running long, some jobs would finish incomplete without any warning or info, etc) to Jitterbit - a very stable product if you give it the recommended server size it needs.
It has made crafting solutions for data movement and transformation quick!
