IBM API Connect Reviews

We use the solution to monitor, process, and manage API services.

We use the product to enforce standards to check and align things with the application design. The tool has enhanced our digital transformation efforts. With the adoption of the cloud, we deploy a lot of APIs on Lambda. We also have APIs deployed on-premise. We use the front-end access of all the APIs on-premise and on the cloud.

The API lifecycle management has helped us to do the version controls and naming of the APIs. The product gathers data to measure API performance. Users monitor the utilization of each API and the response times. It helps manage the environment. The product facilitates development by allowing the developers to go to the portal and test the APIs.

It would be nice to have a SaaS solution that can be deployed into the cloud.

I have been using the solution for many years.

The tool is very scalable.

There's a bit of a learning curve to the setup process. Once the support team gets familiar with it, it is just like any other product.

We started with DataPower ten years ago. Most of our APIs are SOAP APIs. When we started using RESTful APIs, we started using IBM API Connect. It took us a while to adopt API services. I will recommend the solution to people who need to manage their APIs. It's pretty good. It serves our purpose. Overall, I rate the product an eight or nine out of ten.

The API manager of the enterprise exposes common functionalities to the front-end applications, beginning with the frontend of the executives who access clients' information.  The exposition of the functionalities of transferring funds and AFP which need to transfer the money from your account to a client's AFP.  The exposition of the core functionalities to the module of the sale of a product installed on the cloud of AWS, to create an onboarding platform for the client's prospect of the enterprise.

The product has a little use at the enterprise because the APIs have functionality with low use. The next steps are to enforce and grow the use of APIs through the creation of a governance department that aligns the construction's standards and defines the classifications of APIs. 

This is the main goal, to finally integrate the applications that will deploy on the cloud consuming the backends on-premise through IBM API Connect. Having the centralized management of APIs.

The most valuable features are:

1. The centralized management: this provides a management module that can deploy and apply security policies to all APIs, including all the gateways that are deployed on-premises and on any cloud because the gateway component can run at a VMware or in a Kubernetes cluster.

2. The analytics module: this provides a variety of visualizations of the APIs, products, subscriptions, and applications that can be defined for a second, a day, a week, a month. This module is deployed beside the gateway and collect all the traffic.

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. 

We have been using IBM API Connect for six months.

It's very stable.

The solution offers horizontal scalability. The power of the product is the high performance in security tasks done with dedicated hardware.

We implemented it with the official vendor of the product.

Another team selected the product.

We use it for API integration, particularly in conjunction with the One Link solution. One Link is a platform that comes into play during cross-channel communication within the banking sector. For instance, if a customer has an account with Bank A and wishes to withdraw funds from Bank B, it facilitates cross-selling communication between two distinct banks—Bank A and Bank B. Our primary focus is on enabling seamless transactions between different banks, and we also incorporate case and bundle links within our solution.

DataPower Gateway holds significant value for us as it serves as the cornerstone of our enterprise security controls. Even in the absence of published APIs, DataPower Gateway continues to maintain robust security measures. In the event of IBM API Connect experiencing downtime, users can still access APIs through DataPower Gateway, thereby minimizing downtime and ensuring continued service availability for users.

Understanding the architecture, deployment criteria, and communication methods of the installation can be time-consuming. The learning curve is noticeable, especially for new engineers.

We have been working with it for ten years.

I would rate its stability capabilities ten out of ten.

It is highly scalable. On a scale from one to ten, I would rate it between nine and ten.

When there's an open ticket with severity one, the IBM team consistently provides timely support. We are highly content with the support we receive from IBM. I would rate it nine out of ten.

Positive

The initial setup is relatively straightforward.

The initial installation phase may pose challenges as it requires some time to grasp the intricacies. The learning curve is significant, especially for people who don't have experience with it. While the installation may not be easy initially, users can acquire proficiency once they have a thorough understanding of the system. When deploying a new environment, the entire setup typically takes approximately one to two days. Assigning two individuals to manage the deployment process is more than sufficient. For ongoing maintenance of the solution, a single person is capable of handling all the necessary tasks efficiently.

Overall, I would rate it ten out of ten.

We use IBM API Connect for the external gateway for integration, and it is for multiple customers with the external button.

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.

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.

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.

We are working with the big and the medium businesses.

The support is good and active. I rate the technical support a nine out of ten.

Positive

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.

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.

The primary use case of IBM API Connect is for API monetization in the banking and financial sector. This involves API management and creating APIs for financial institutions, which is the main use case. Another use case is having all API integrations in one place. A third use case is opening an API and sending the documentation to external third parties.

The solution provides a common place for all APIs, allowing for easy sharing and exchange of information between internal and external stakeholders. So, the solution functions as an API management platform.

I am currently investigating the weaknesses of the solution, specifically in its on-premise infrastructure. One of the main concerns is its performance, as we have noticed some cases of resource consumption that may be related to our setup. We have concerns regarding the handling of asynchronous APIs and events in the architecture, particularly in the financial sector, where this is becoming more common. While this is well-addressed in MuleSoft, we are uncertain about how IBM API Connect handles this use case, as it does not appear to be addressed in the available documentation.

I have been using IBM API Connect for two years. My customers use the solution. I work for two companies, and none of them are partners. It is just a solution used in the banking sector.

Stability-wise, I rate the solution a seven to eight out of ten.

The solution's technical support has been very responsive. I had no problems with them. I would say it's a very good and strong point of the platform.

It is an expensive solution. The licensing model is based on a per-subscription and per-subscriber end-user basis, meaning the price is determined by the end-users of the platform. Also, the price may be higher compared to some other competitors.

There are some performance issues and issues related to asynchronous APIs. So, now we are investigating these issues since they are critical ones. Owing to the aforementioned reasons, I rate the overall product an eight out of ten.

We use IBM API Connect primarily to expose APIs for various information systems in Terra and to integrate with our audit partners.

The main benefits of IBM API Connect for our API life cycle management are the core API functionalities, the developer's portal, and robust security capabilities.

IBM API Connect's security protocols enhance our data protection strategies by offering end-to-end security, mechanisms to counter common attacks like DDoS, and the ability to define policies for API groups to control traffic and prevent unwanted access to our systems.

We have encountered challenges with IBM API Connect, particularly during significant upgrades.

These upgrades demand substantial labour and financial resources, including consulting services from IBM.

I'd like to see increased flexibility, more frequent updates with new features, an efficient upgrade process, and additional AI capabilities for future releases.

I have been using IBM API Connect for the past five years.

Currently, around ten to fifteen people in our company are using IBM API Connect, and we plan to increase automation in the future to reduce manual effort.

My experience with IBM's technical support has been challenging. Accessing support and navigating their processes has limited flexibility. However, after successfully complying with their procedures and exercising patience, they know how to handle issues efficiently.

Neutral

Before using IBM API Connect, we worked with similar integration products, particularly an ESB from IBM, which was crucial in creating system integrations.

Setting up IBM API Connect initially was challenging, as expected, due to its complexity.

Compared to some other products on the market, implementation took about six months.

IBM API Connect has provided significant financial and operational benefits for our organisation.

It has facilitated integration across systems and enabled cross-organisational processes. As for the time it took to record a return on investment, we started seeing tangible benefits within approximately two years.

IBM API Connect has dramatically aided our AI-driven projects by increasing developer productivity and facilitating the development process using AI tools. It helped us automate sub-processes and perform thorough analysis for operations and security.

I would suggest considering IBM API Connect for enterprises focused on security and enhanced functionality, especially if they need rapid implementation. If they're looking for more advanced capabilities or a broader solution, I recommend exploring options like Google Apigee or MuleSoft Anypoint Platform. Each product has its strengths and focuses, so aligning with the organization's specific needs and priorities is essential.

Overall, I'd rate IBM API Connect an eight out of ten.

We're trying to make our business available on the net so that partners can connect, and distributors can use our services.

Its speed and performance are valuable.

It's based on a little bit dated architecture. A lot of evolution has happened after that. It's an evolving field. Kong is a Kubernetes-based platform. Kong runs on Kubernetes, but all the other ones are in microservices. So, there's a lot of improvement that can be done.

I've been using it for three years.

It's stable.

It's good. There are a lot of other good products also.

We didn't access their support much.

It's pretty much straightforward. We just downloaded and installed it.

I'd rate it a six out of ten.

We deploy APIs to expose the BFFs of mobile apps, and this is mainly in the cloud. All mobile apps consume the APIs of your BFF. On-premise, we have APIs that expose services and mainly functionalities, such as the balance of the client or the customers or the products.

One of the most valuable features is the easy-to-use web interface.

Documentation for the CLI is not very complete. Also, the support could be improved, and we have had several problems with backing up and restoring the product.

We have been using the solution for two or three years.

The stability of the solution is good.

The scalability of the solution is good.

IBM support is not available in Chile, so we must go through other countries to get a response from customer support.

I would rate the setup as a medium in difficulty. 

The solution was first set up with the help of IBM, but when we moved to another environment, we followed the initial instructions given by IBM and implemented it ourselves. 

We used Bamboo as a pipeline for automatic deployment of the API. The deployment took four hours.

The product is easy to use, but the installation is not easy. We have a team of three architects who maintain the product. I would rate this solution as an eight out of ten.