We mainly use it for API orchestration, basic gateway features, and data features. We use it just for orchestration and gateway functionalities.
Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
173 reviews
from
and
External reviews are not included in the AWS star rating for the product.
A good option for API management
What do you like best about the product?
It is really easy to create, test and deploy all of our APIs in a single place.
What do you dislike about the product?
As of now I did not find any drawbacks. Although documationation can be improved.
What problems is the product solving and how is that benefiting you?
It helps our organization to create and manage all our APIs and integrate those APIs to different external resources.
Reached my expectations
What do you like best about the product?
Security , open shift environment and it's high scalability
What do you dislike about the product?
Complexity while setting it up and felt it like challenging
What problems is the product solving and how is that benefiting you?
Security and managing the API's . It's briniging all of the API's toghether to one place that's how it is benefitting to me
Offers basic API orchestration and provides robust security and governance features
What is our primary use case?
How has it helped my organization?
Our client has a vendor contract with IBM and uses various IBM products, including API Connect. So, it's more of a forced usage within the organization.
So, it fulfills the basic needs.
What is most valuable?
It acts as a central gateway for both external APIs and underlying systems. It's basically a central middleware for hosting APIs to the internet and consuming APIs from internal systems.
It provides central governance for any APIs going outside the network, ensuring security and a common contract for API definitions.
What needs improvement?
We're good with things like API hosting, console features, etc. However, compared to Azure API, IBM API Connect lacks some things offered by the other platform.
I wish it covered the entire API lifecycle, including governance and management, more comprehensively.
For how long have I used the solution?
I have been using IBM API Connect for the past six months due to a client engagement.
We use the latest version.
What do I think about the stability of the solution?
I would rate the stability an eight out of ten. It has good stability.
What do I think about the scalability of the solution?
While Azure API Management offers configurable scalability, IBM API Connect relies on Kubernetes clusters. This might seem manual and require defining cluster instances upfront, but it's completely customizable and not on-the-fly scaling.
It's completely custom-driven, not on-the-fly scaling, which some may consider cumbersome.
Overall, I would rate the scalability an eight out of ten.
Almost all applications we've been exposing lately go through this middleware, so it's used extensively. There are around sixty applications directly using it, but six Kubernetes clusters serve those applications.
It's heavily used for integration, including system-to-system integration and product integrations.
Our usage has been increasing year-on-year based on our needs.
How are customer service and support?
The customer service and support. are good. They respond promptly to any issues requiring assistance, and they have an SLA for response times.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We have a partnership with IBM for some products, but for IBM API Connect, we're just end users.
I used Azure API and then Microgateway. We use IBM API Connect because the client is an existing user of API Connect for another client's project. Their organizational practices favored using the same solution, so we had to go with IBM API Connect.
How was the initial setup?
I would rate my experience with the initial setup a seven out of ten, with ten being very easy to set up.
It wasn't complex overall, but the initial API creation had some challenges regarding security implementation. After that, it was much easier. We followed the template, but sometimes the page would close unexpectedly.
We faced some initial setup issues. Initially, understanding and implementing the right way to achieve API-level security, etc., was a bit tricky.
The documentation is decent, and they offer some provider-based human support, so that's sufficient.
We have on-premises installations for some applications hosted in Kubernetes clusters, and the on-premises Kubernetes cluster can be hosted anywhere. It's a containerized cluster deployment.
What about the implementation team?
IBM API Connect was already an existing middleware for the client, and we only expanded it for our new digital transformation project. So, the deployment process wasn't relevant to my experience.
Only two people manage it. They handle the entire API lifecycle, including hosting and management, across four different environments. They're DevOps engineers, playing both development and operations management roles.
What was our ROI?
There were two things: governance and security. This product helped greatly in both areas.
It is used across the entire organization, so the ROI is a hundred percent. Because if we couldn't have hosted an API gateway on some applications, that would be a failure. Now, any new application they build, any new product, can easily expose the appropriate API, making it worth the initial investment.
What's my experience with pricing, setup cost, and licensing?
It can be quite expensive. It's okay for large-scale usage but quite expensive for smaller-scale implementations.
Overall, I would rate the pricing an eight out of ten, with ten being expensive. The pricing is fixed, not a floating model.
What other advice do I have?
If it's for a large-scale API ecosystem, IBM API Connect is a good choice. It's manageable, reliable, and offers extensive features.
Mainly understanding API gateway principles. If they grasp those, they can use this product. So, some background knowledge is advisable.
Overall, I would rate the solution an eight out of ten.
A very robust tool that needs to improve its user interface
What is our primary use case?
My company used to work with IBM API Connect for a customer in Greece to run a public sector company from whom we developed a new architecture based on API management last year for the logistics or transportation domains. For the aforementioned project, my company designed a solution based on IBM API Management for the logistics sector of a company all over Greece.
What is most valuable?
The most valuable feature of the solution stems from its ability in the area of message transformation, meaning it is very easy when you have to transform a message to XML or transfer it automatically from JSON and vice versa. The solution is very scalable. The solution works very well even if you have a small number of users. Our company also tested its use with a large number of users, consisting of more than 2,000 users, and it was very nice to use. The tool is very robust.
What needs improvement?
The administration of the user interface and the technical documentation are areas of concern in the solution where improvements are required. The solution's technical documentation should be a little bit easier to understand, and it is a traditional problem with all IBM products. The technical documentation is a bit too difficult to understand, and it is also not easy to read.
For how long have I used the solution?
I have been using IBM API Connect for three years. I operate as an independent consultant.
What do I think about the stability of the solution?
Stability-wise, I rate the solution an eight out of ten.
What do I think about the scalability of the solution?
It is a very scalable solution.
The meaning of the size of the companies in Greece is very different from what it is in other parts of the world, like the UK or Germany. The tool has around 2,000 users. I don't know if 2,000 users are found in small, medium, or large enterprises, but in the UK, it is a number to describe a small business, while in Greece, it is considered a large-sized company.
How are customer service and support?
I rate the technical support a six out of ten.
How would you rate customer service and support?
Neutral
How was the initial setup?
I rate the product's initial setup phase a five on a scale of one to ten, where one is a difficult process, and ten is an easy phase.
The solution is deployed on an on-premises model. The client with whom I work operates only on an on-premises infrastructure. My client is very demanding when it comes to operating on an on-premises infrastructure. My client is adamant on having on-premises infrastructure owing to security concerns.
What's my experience with pricing, setup cost, and licensing?
I rate the product price a seven on a scale of one to ten, where one is a low price, and ten is a high price.
What other advice do I have?
I rate the overall tool a seven out of ten.
Which deployment model are you using for this solution?
On-premises
My review on IBM API CONNECT
What do you like best about the product?
The first thing i would love to mention about this software is the ease of integration, i was able to easily integrate it with our company website and during the process of integration, i found out that IBM API has a huge web of external systems that it could be easily integrated into and not just a company website. with IBM API CONNECT . we were able to easily control, manage, create, anaylse all our API link services... it allowed us to easily upscale and downscale at any moment of need... the tool that helped us in easily creating these API was very user-friendly without it taking so much time to set up. IBM API CONNECT provides us with a very strongly secured gateway to manage all our internal to external data send and requests... The customer care support team was also very responsive and very professionally knowledgeble
What do you dislike about the product?
The software implementation and structure can get so complicated at any moment especially with a lot of API on board.. which does lead to more hands on deck
What problems is the product solving and how is that benefiting you?
The biggest problems we had issue with was security .. IBM API CONNECT really saved our side on that.
A great tool connecting the dot
What do you like best about the product?
IBM API connect is a great tool that has helped us in fetching, analysing data securely and hassle free. It's a great tool to meet our business day to day activities.
What do you dislike about the product?
I don't have any challenges using the API software so far.
What problems is the product solving and how is that benefiting you?
IBM API Connect help solve the problem of fetching data and information from one point to another securely and faster compare to manual data integration. It has helped to faten the business process by fetching data securely and faster
Robust API management that facilitates seamless integration and communication, empowering businesses to efficiently manage, secure, and optimize their APIs for enhanced digital capabilities
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
Understanding the architecture, deployment criteria, and communication methods of the installation can be time-consuming. The learning curve is noticeable, especially for new engineers.
For how long have I used the solution?
We have been working with it for ten years.
What do I think about the stability of the solution?
I would rate its stability capabilities ten out of ten.
What do I think about the scalability of the solution?
It is highly scalable. On a scale from one to ten, I would rate it between nine and ten.
How are customer service and support?
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.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup is relatively straightforward.
What about the implementation team?
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.
What other advice do I have?
Overall, I would rate it ten out of ten.
manage you API in a central platform.
What do you like best about the product?
we are using IBM API connect for managing all our prod as well as pre production API, API connect offers a single platform to manage all our API's with central control. it's quite easy to use and very helpful in monetering our API with real time updates.
What do you dislike about the product?
While there are so many good feature that API connect offers still i think setup time to add API can be time consuming and requires support from tech team.
What problems is the product solving and how is that benefiting you?
helping our team to manage and create API for prod as well as non prod environments.
Powerful API gateway solution
What do you like best about the product?
Easy to define APIs mapping and implementation of features in order to cover all uses cases
What do you dislike about the product?
Maybe it's complex to manage large systems
What problems is the product solving and how is that benefiting you?
Balancing between CPDs and custom routing to each platform. Security and from time to time transform requests/responses.
IBM API Connectivity and configuration
What do you like best about the product?
End to end API management , robust security features like OAuth and API key management
What do you dislike about the product?
Initial setup is little complex and reporting customisation is little challenging with basic skill set on the same. Cost is another factor when it comes to license
What problems is the product solving and how is that benefiting you?
helps manage the entire API lifecycle, from design and creation to testing, deployment. Also security is very good which is very crucial in this era of tech
showing 41 - 50