IBM App Connect Review

It is reliable and the number of endpoints is valuable. Multiple developers should be able to work in the same project.


What is most valuable?

Its reliability and the large number of endpoints for connectivity are valuable features.

What needs improvement?

I would like the ability for more than one developer to work on the same project (source control/branch merge). If the project has more than one orchestration, you should be able to have different people working on each.

For how long have I used the solution?

I have used the product for about nine years (since before Cast Iron was acquired by IBM).

What do I think about the stability of the solution?

We are running the HyperV version and have had no problems with stability. Though if not designed well, the projects can definitely run out of resources when processing.

What do I think about the scalability of the solution?

It scales well. We are considering moving to the cloud version, as only one or our endpoints is local and all the others are SaaS endpoints.

How is customer service and technical support?

They give excellent technical support.

How was the initial setup?

It is easy to set up. HyperV has OVF that you deploy to a VMware ESX Server.

What's my experience with pricing, setup cost, and licensing?

IBM has gone back and forth on licensing for this product. Make sure you get the licensing that lets you have unlimited endpoints; otherwise, you will need to account for each separate endpoint in your licensing costs and adding more automation has a price impact.

Which other solutions did I evaluate?

We evaluated MuleSoft and Dell Boomi.

What other advice do I have?

Your developers should be well-versed in XML and XSLT. These are behind everything.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest
Sign Up with Email