What users are saying about
24 Ratings
27 Ratings
24 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 7.5 out of 101
27 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8.3 out of 101

Add comparison

Likelihood to Recommend

Apache Camel

For basic publish subscribe use cases, Apache Camel is the clear winner
Akmal Muqeeth profile photo

InfoSphere

Information Server is extremely useful to replace manual developments that require a lot of coding effort. It significantly increases the productivity of the initial development and the future maintenance of the processes since it has a visual development environment with self-documentation.
Karina Gonzalez profile photo

Feature Rating Comparison

Data Source Connection

Apache Camel
InfoSphere
8.7
Connect to traditional data sources
Apache Camel
InfoSphere
9.6
Connecto to Big Data and NoSQL
Apache Camel
InfoSphere
7.7

Data Transformations

Apache Camel
InfoSphere
9.6
Simple transformations
Apache Camel
InfoSphere
10.0
Complex transformations
Apache Camel
InfoSphere
9.2

Data Modeling

Apache Camel
InfoSphere
8.7
Data model creation
Apache Camel
InfoSphere
9.0
Metadata management
Apache Camel
InfoSphere
8.6
Business rules and workflow
Apache Camel
InfoSphere
9.0
Collaboration
Apache Camel
InfoSphere
8.4
Testing and debugging
Apache Camel
InfoSphere
7.2
feature 1
Apache Camel
InfoSphere
10.0

Data Governance

Apache Camel
InfoSphere
9.6
Integration with data quality tools
Apache Camel
InfoSphere
10.0
Integration with MDM tools
Apache Camel
InfoSphere
9.3

Pros

  • Producing to and consuming from any messaging system
  • Message type conversion
  • Large support library
Akmal Muqeeth profile photo
  • Great for data warehouse
  • Gathering an analytics of data is great
  • Metadata
No photo available

Cons

  • I find the "seda" endpoint to be less obvious that it is doing multi-threading than Spring Integration's executor mechanism.
  • Integration with Spring Beans is pretty good, but I believe SI's is a bit better (for obvious reasons, both being Spring products).
  • SI's use support is probably a bit better/faster and I believe the user base is larger so that there are most questions/answers for SI on StackOverflow
No photo available
  • Lack of a strong web development environment.
  • Metadata propagation in Jobs is somewhat complex.
  • The possibility to develop jobs in Parallel and/or Server Engines is confusing.
Karina Gonzalez profile photo

Likelihood to Renew

No score
No answers yet
No answers on this topic
InfoSphere8.0
Based on 1 answer
  • Scale of implementation
  • IBM techsupport
No photo available

Usability

No score
No answers yet
No answers on this topic
InfoSphere9.0
Based on 1 answer
Very usable and user accessible
No photo available

Performance

No score
No answers yet
No answers on this topic
InfoSphere8.0
Based on 1 answer
Information does load quick, but it depends on what's being done, the backend database seems to be the biggest bottleneck
No photo available

Alternatives Considered

We did a comparison of the two products with an example application that tested about 10 distinct EIP pattern. We wrote Camel in XML and Java DSL and SI in XML. This was about 3 years ago. At the time, I found the threading model in SI to be more intuitive and Camel's seda. However, Camel's documentation at the time was far and away more complete (Wiki pages for Camel vs looking through XML schema for SI). Since the SI has improved their documentation. The main factor that I believe still sets Camel apart is the Java DSL. Writing routes is complicated enough, but doing so in XML would be just painful.
No photo available
I particularly believe that Information Server, especially DataStage, is superior in many aspects to the Oracle Data Integrator tool. Several market analysts such as Gartner and / or Forrester better position DataStage on the Oracle solution.
Karina Gonzalez profile photo

Return on Investment

  • 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.
No photo available
  • Productivity of the development of integration processes.
  • Better documentation and governance.
  • Reduce training costs of various technologies.
Karina Gonzalez profile photo

Pricing Details

Apache Camel

General
Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details

InfoSphere

General
Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details