Please share with the community what you think needs improvement with IBM API Connect.
What are its weaknesses? What would you like to see changed in a future version?
The documentation needs to be a bit better. It's very sequential, however, I don't understand what options to choose for certain tasks. I need to read all of the documentation to find what I need. It's easier to look at recommendations or to watch Youtube videos that show specific examples. There needs to be more in the toolkit to complement the product. We could have more features, for example, for queries to the platform.
The solution would be better if it had cloud functionalities. It would be very helpful if it supported Azure and/or AWS marketplaces. Right now, if I want to set up something in Azure, I need to set up a VM from scratch instead of just being able to have it be supported and integrated.
We've had some issues upgrading to the latest version of the solution. The documentation could be improved. When we download a fix that was expected to be seamless to install, it wasn't. In the past, it was easy just to go to any product and download the documentation. If you had the license, you download the product, install it, look at the documentation. Only for specific cases would you have to reach out to support. Now it is like we know that, for these products, we're going to have to call or engage at some point with support. It's painful right now. It's not a smooth installation. A hybrid cloud enablement would be very useful. We tried to stand up a gateway in IKS and we were told by support that that was not possible. Yet, the technical people, the designers of the solution, started saying, no, you can actually do it. However, they never said is supported, so I was never sure where the solution stands on hybrid clouds. The answers that sometimes are provided are not very comforting. If it isn't a full commitment it isn't going to work. They need to make it a product that can be downloadable and installable and workable without having to engage with them directly.
The automation and the simplicity could be improved. They could also have more frequent additions. I would like to see the simplicity improved to make it very easy to deploy and to make it very easy for the regular developer, not an API special developer. I would like the developers to be able to develop APIs and to make them more accessible. I would also like to have a DevOps built-in process that is very fast and easy. The monitoring suite should be ready-made and not have to tailor-make my home.
The initial setup and installation could be easier. The price could also be better. I would like to see monetization of support, a monetization billing engine, and monetization within the product in the next release.
The developmental process is not quite user-friendly. IBM should improve the customization of the API Connect. The price could be reduced, it's expensive.
Improvements depend on your perspective and what you need the API to do. I think it has room for improvement because, for example, there's nothing to show that other teams might be dumping the same thing and you have no way of knowing if it's redundant. I feel that sometimes different versions of the same thing are put in there. Although there may be slight differences like including some extra fields, at the end of the day, you're almost dumping the same API again into API Connect. At some point the product should be able to tell you that there is already a similar API there and whether you're dumping an API that's almost identical to what is there.
One place that I think the product could improve is that it could be lighter on computing resources and cheaper. We did not expect to have to add additional services for data processing.
It would be helpful to have access monitoring. The initial setup is complex.
The product can be improved in the following areas: 1. The monetization because it doesn't include an online method to pay through a web system or with a credit card, where the analytics can be calculated. 2. The integration of an API gateway that implements the sidecar pattern, which can be deployed in cloud applications, and expose the microservices directly in each pod, this can be more decentralized components. All of these areas can be improved.
There is room for improvement in the reporting and monetization. With monetization, I want to be able to provide my own pricing and platform. I would like them to add hooks into the API. E.g., it should be able to check credit, then limit access to people who don't have credit anymore. They need to have more training for people.
In terms of what needs improvement, some of the product documentation could be better.
Extracting the data could be improved. My team members sometimes find it difficult to get something out of this solution.
I would like to see support for non-Java based services. We struggle a bit to be able to deploy and connect our .NET services because of things like data types. We had to map a couple of things. For one solution provider, we had to move them to .NET Core before we could use it properly. I would like to see more agnostic tool service platforms rather than moving it more towards Java or open source.
They seem to have left out a feature for microservices and also a certification module for OIDC. So it would be a good idea for the authentication module to have OIDC certification.
It still does not support open API 3. Another problem is the designer. I want the whole solution to be on the cloud. For the installation, I have to install locally. There are many improvements it needs if I want to implement a MockServer or sandbox. In the future, I hope it will be more intuitive for building a MockServer. 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 old designer should be less complex and more simple or intuitive for you to search as well.
It is still a very new product. We're still finding our feet on the latest version of it because it gives you the capability to move into the cloud. We have not yet taken that leap into cloud because of the uncertainty of what the moving parts are, and that's why we'll have to wait and see. I would like to see more stability, however, and I do believe the newer version will offer that.
IBM is also a bit pricey. On top of that, they have bugs that need to be fixed.
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. A more user-friendly portal could be helpful. Something you won't really get lost in. For example, other APIs make it so easy to do a couple of things from the portal, not at the management portal itself. Maybe if IBM can improve on that, it would be most helpful.
Business applications could be exposed to users.
Automation for our Domino applications could be improved.
I'm researching API management solutions. My use case: using a microgateway in containers.
Should I choose IBM API Connect or Apigee? I'm not able to see the API Connect's value.