IBM API Connect Pros and Cons

The most valuable feature is the security we get from this solution. I know of a bank that uses it to ensure that everything is secure. The second feature I like is the retail environment, where we actually want to be able to provide as many suppliers and consumers with APIs as possible. If you are well-trained in the writing of RESTful API's, you can actually publish an API in a matter of minutes, test it, and publish it.

The developer portal has been the most useful feature.

The solution is very scalable because it's on the cloud.

This product is well integrated with other products. Its ability to interact with IBM Secure Gateway and other integration products is the core feature. Also, the lead time to put it into production is relatively short .

The solution is very stable.

The ability for all of our web applications to share standard functions and documents easily is valuable.

Easy to configure security and generate API keys.

Policy configurations are pretty easy.

I have found the API Management to be most valuable.

The new version is very unstable.

Like any typical IBM infrastructure setup, you need to learn to set it up yourself. It's not one of those simple zip files or an archive unzip and you're up and running in some few minutes. Knowledge to set it up is key.

In the next version, I don't know if they've already been included it or not, but the designer and all the tools should be on the cloud. I don't want any external installation or local installation.

The solution is not scalable.

Automation for our Domino applications could be improved.

Components, like caching, should be implemented as policies, not requiring dependency on an external solution.

Business applications could be exposed to users.