We have implemented this product in different domains, such as insurance and banking.
IBM API Connect - Full lifecycle API management
IBM SoftwareExternal reviews
174 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Quite flexible and provides excellent performance for API gateway
What is our primary use case?
What is most valuable?
It's quite flexible and easy to deploy, especially for beginners. It has almost all the features that an API gateway should have.
What needs improvement?
The only disadvantage I can see is that it requires heavy hardware support, which can be considered quite expensive.
In terms of new functionality, I think the analytics can be improved in V10. The analytics feature was better in the older version, 2.18. But in V10, it's not as flexible. When exporting analytics as KSP or JSON, it's not well formatted. They can work on enhancing the analytics part. Additionally, they can focus on reducing the hardware cost.
For how long have I used the solution?
I have been working on IBM API Connect for the last six years. I am using V10.
What do I think about the stability of the solution?
It's very stable. Previous versions were not as stable, but now, starting from 2018, I can see that the product is very stable. I would rate it a ten out of ten.
What do I think about the scalability of the solution?
It is scalable. I would rate it a ten out of ten. Any number of users can utilize the solution. All of our clients are enterprise clients.
How are customer service and support?
So far, whatever the PMR I have raised, IBM has given a solution that may be complicated, and it might take time, but in the end, we got the correct solution. The response time can be improved.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I also have experience with Red Hat 3scale API gateway.
IBM API Connect is much much better. In terms of features, there are some limitations with 3scale. Additionally, the support for Red Hat 3scale is not as good. Even the documentation provided by Red Hat is not as comprehensive as IBM's strong documentation. If you're a beginner developer and referring to the IBM Knowledge Center, you can easily develop your API, but that's not the case with Red Hat. Red Hat's documentation is still not as mature as IBM's.
How was the initial setup?
The initial setup is quite easy. The deployment of the environment and the solution itself is quite easy. The deployment itself can be done in a few minutes. Let's say 30 minutes for deployment and 30 more minutes for configuration. Within one hour, your environment is ready.
One person is more than enough for the deployment.
What's my experience with pricing, setup cost, and licensing?
The pricing for 3scale is definitely cheaper. However, for enterprise-level projects, we don't recommend 3scale. If the client is medium or small and requires a basic API proxy or minimal transformation, we propose Red Hat. But for big, mature clients with complex solutions, we recommend IBM API Connect.
The pricing for us on a yearly basis. But currently, IBM API Connect also provides it as a cloud service, where you pay as you use it. That provision is also available. Only the license is covered. There are no hidden costs or extra charges.
What other advice do I have?
I would suggest that if you're looking for stability and excellent performance for your API gateway, you should definitely choose IBM API Connect.
Overall, I would rate it as a ten.
Along with good support, it is a powerful and comprehensive tool for building APIs
What is our primary use case?
We use IBM API Connect for the external gateway for integration, and it is for multiple customers with the external button.
What is most valuable?
IBM API Connect is a tool that helps enterprises to build an API for an enterprise. But we use it for user experience and channel integration. We use the features of building the APIs for the experience. API is exposed to different channels like mobile channels, automatic channels, portal channels, and different channels. We use the solution's management capability to define monetization and have different plans used to control IBM API Connect. So we use the full-fledged API management tool, especially for the development, monetization, publishing, and installation parts. Also, it's all deployed on an OpenShift platform.
What needs improvement?
There are two disadvantages to the solution. Firstly, the pricing model, when compared to other open sources, is high. Secondly, the availability of resources in the market, specifically the developers available in the market, is not so much. So, the aforementioned areas need to be considered for improvement.
For how long have I used the solution?
I have been using IBM API Connect for five years. My company has a partnership with IBM. Also, I am using the solution's latest version.
What do I think about the scalability of the solution?
We are working with the big and the medium businesses.
How are customer service and support?
The support is good and active. I rate the technical support a nine out of ten.
How would you rate customer service and support?
Positive
How was the initial setup?
The installation is not easy. However, on a traditional VM, it is acceptable. It can get complex since it's required to have multiple components deployed, and I think it is necessary to have the technical experience to do a global configuration for production. You need some access to get the benefits of the enterprise and the platform. Also, such things are expected because the solution is an enterprise-grade player. For such a tool to have the benefits of stabilization to support the high demand of workloads, it should have a robust configuration. That is why it's not a simple configuration. I'm talking about the big enterprise, not the medium or small enterprises. It's not suitable for medium, small, and micro-enterprises because the cost of setup and the solution, along with the license, may not be suitable for small businesses.
The solution is deployed on the cloud and on-premises. Sometimes it's private, and at times it's both also. So, you have one public and a private cloud.
The deployment can take up to two to three weeks, and I am saying this considering previous projects, connectivity, and deployment, so I am talking about the time taken to build the environment.
What about the implementation team?
What other advice do I have?
The solution is a very, very powerful tool. It has many, many capabilities, apart from it having many, many adapters and integration with the backend to provide you with a comprehensive portal development portal application. This comprehensive portal application can be used by the developers of API since API is a fast and powerful tool. In addition, the analytic part of the tool provides you with full analytics and defines SLA for the APIs, and you can generate the analytics to get statistics about the utilization of API, which most people use. This tool is very, very comprehensive and very, very beautiful. It's very easy to use. And in addition to that, it is an API management tool deployed on an OpenShift platform to give you the capability of containerization for sustainability and agility. So, it's part of the tool.
Overall, I rate the solution a nine out of ten.
Turbulent journey which started with the inception of v2018 and continuing with v10 LTS releases.
What do you like best about the product?
Stability offered by the gateways in runtime environment .
Industry standards adoption and adherence to RFC
Ease in API development and allows customized policy flows when compared to other API manangement solutions
Industry standards adoption and adherence to RFC
Ease in API development and allows customized policy flows when compared to other API manangement solutions
What do you dislike about the product?
Upgrades and fix pack releases are not backward compatible .
OAI 3 standard adoption is delayed when compared to other API management solutions .
Quick Adoption of industry standards
OAI 3 standard adoption is delayed when compared to other API management solutions .
Quick Adoption of industry standards
What problems is the product solving and how is that benefiting you?
OAuth Security implementation for the API tech stack within our organization . Ease of adopting new security standards which leads to a secure API platform for business to handle confidential data.
Highly scalable and can handle large volumes of API traffic
What do you like best about the product?
Wide range of features, including API creation, testing, management, security, and analytics. Supports both REST and SOAP APIs. offers a range of security features, including OAuth and SSL/TLS support, role-based access control, and IP whitelisting.
What do you dislike about the product?
We are using most Microsoft products so integration with Microsoft is a bit complex. IBM API Connect can be limited, which can make it challenging for new users to get started. IBM API Connect requires a license, which can be a significant expense for smaller organizations or startups. API Connect is resource-intensive, which means it may require additional hardware and software resources to run effectively.
What problems is the product solving and how is that benefiting you?
IBM API Connect provides a centralized platform for managing APIs, which can help organizations to streamline their API management processes. This can help to reduce complexity, improve efficiency, and increase the consistency of API management.
Secure and saleable Product
What do you like best about the product?
Easy to configure and monitor all API's traffic and logging
What do you dislike about the product?
Logging should be more detailed, like individual API traffic and busy API dashboard
What problems is the product solving and how is that benefiting you?
Single platform to manage all domains and sub-domains API and security also configuration and logging
Excellent integration tool with fast implementation
What do you like best about the product?
I like that it is easy to integrate and easy to use, it is very reliable and supports various devices. I liked this app.
What do you dislike about the product?
Difficult to navigate at first and the panels show little information.
What problems is the product solving and how is that benefiting you?
A solution that helps us with the management and integration of applications and shows great performance.
IBM api connect is a simple and easy to use service
What do you like best about the product?
IBM api connect is a simple and easy to use service with huge scope of features to build and manage your APIs
What do you dislike about the product?
The interface can be much more interactive and designed well. Also the downtime can be minimised
What problems is the product solving and how is that benefiting you?
I used api connect to create and manage simple APIs as a POC
It was woderful expereience
What do you like best about the product?
I feel it is much more secure and easy to use
What do you dislike about the product?
I have not feel anything disliking, It is good
What problems is the product solving and how is that benefiting you?
It helps me to route the API to the backend service
Great technology to enhance skills
What do you like best about the product?
Api manager test,stage,prod and recent migration from v5 to v10
What do you dislike about the product?
Onboarding of apis in prod and api manger sometimes quite difficult to navigate.
What problems is the product solving and how is that benefiting you?
Subcription of apis and the data migration
One of the best Integration solution with IBM API Connect
What do you like best about the product?
Ease of usage, Easy to implement this solution
What do you dislike about the product?
Commercially very expensive. It has to be flexible in commercial modelling
What problems is the product solving and how is that benefiting you?
Its solving integration of my machine critical workloads
showing 91 - 100