We just raised a $30M Series A: Read our story

IBM API Connect OverviewUNIXBusinessApplication

IBM API Connect is the #2 ranked solution in our list of top Integration Platform as a Service providers. It is most often compared to Apigee: IBM API Connect vs Apigee

What is IBM API Connect?
The IBM API Management family of products gives you software tools to create, manage and share application programming interfaces (APIs) in a secure, scalable environment. Available in both on-premises and cloud solutions, its detailed analytics and operational metrics allow you to monitor API usage to ensure that the developers' needs Ð and applications using the API Ð are being met.
IBM API Connect Buyer's Guide

Download the IBM API Connect Buyer's Guide including reviews and more. Updated: October 2021

IBM API Connect Customers
M2M Technologies Inc.
IBM API Connect Video

Pricing Advice

What users are saying about IBM API Connect pricing:
  • "API Connect's license cost could be a little lower. But, unfortunately, there aren't many open-source API gateways. Ideally, some new developers could come up with a minimum-functionality open-source solution."
  • "API Connect is quite pricey."
  • "I haven't seen anyone go from on-premise to the cloud. In fact, I am seeing people go from the cloud to on-premise because the costs can quickly grow on the cloud."

IBM API Connect Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
VV
Consulting architect at a tech services company with 501-1,000 employees
Real User
Stable and easy to set up but might be too costly for small businesses

Pros and Cons

  • "API Connect's most valuable feature is its ability to act as a gateway. It's very easy to configure security and everything else in it. You don't have to kill yourself implementing custom configurations."
  • "One thing about API Connect that could be improved is the security schemes. There are so many security schemes, and from a product perspective, IBM could improve the user experience of the configuration security scheme."

What is our primary use case?

My clients mainly use API Connect as an API gateway. A lot of the backend services need to be exposed to other parties, mobile devices, interfaces, etc. 

What is most valuable?

API Connect's most valuable feature is its ability to act as a gateway. It's very easy to configure security and everything else in it. You don't have to kill yourself implementing custom configurations. Sometimes the customer wants to incorporate their identity provider, and API Connect handles that without any problems. 

What needs improvement?

One thing about API Connect that could be improved is the security schemes. There are so many security schemes, and from a product perspective, IBM could improve the user experience of the configuration security scheme. It does what it is supposed to do, but it could be easier to configure. The junior developers sometimes find it a bit confusing to configure even though they understand the concept.

And another thing is that I don't know the security policies that we have. For instance, we have a service account, which is needed to connect to some other services. So in those cases, I find it a bit hard to tweak things in the API gateway. And one could argue that it is not the right thing to do with the API gateway. It has a different place to be, which could be why they haven't put it there. But sometimes, you have to tweak around that, and I find it a little bit hard to do that. So if they could accommodate that in there, it would be better for some people.

For how long have I used the solution?

I've been using it for the last four years on and off. The last time I deployed it was a few months ago.

What do I think about the stability of the solution?

API Connect is reliable.

What do I think about the scalability of the solution?

API Connect is scalable, but I've found that everything is more stable if you reset the server every 40 or 45 days. Once, we had an incident in which we were unsure about what happened, but it crashed after 60 days. We didn't know the reason. It could've been a mistake in the product implementation. We don't know what happened, but this particular incident occurred two times. After that, we began restarting it every 45 days. So that's the resilience part, but the scalability part works without a problem.
Another thing is that we don't know all of the use cases that we have worked on before, so we didn't go for automatic scaling of the API gateway. That's done in the backend services. So I'll be honest to say that we haven't explored the auto-scalability of API Connect much. Instead, we put that on full throttle. This can cause a bottleneck if we play around with it, so we didn't take many risks. We put that on full throttle and did the tweaking in the backend services. That's how we did it in the past.

How are customer service and support?

I've interacted with IBM support many times. They're good. They get back to you within 12 or 14 hours after you initiate a ticket. IBM support will get on a call with you if needed and guide you. It's no problem. They provide the same level of support to everyone. 

How was the initial setup?

Setting up API Connect is a straightforward process. Maybe it seems more manageable because I've been taking baby steps rolling it out for the last few years. So when we talk about the latest version, it's not a headache if you follow the documentation. Even for an operations person, it's a piece of cake. 

It takes a minimal amount of time to deploy as a product. Including the processes for the organization, installing the product could take half a day. And when we ask the Ops team to do it, it usually takes half a day for them to do it. They have to document the IP and keep a log of what they're doing. 

API Connect itself does not require any maintenance. But when our teams write the business logic into it, that usually requires some support and maintenance. So a team of two people looks after the whole setup. And they work in shifts. Usually, it works on an onshore-offshore model. So one person from the onshore team will be supporting it for some time, and when he goes off, the other person comes up. 

What's my experience with pricing, setup cost, and licensing?

API Connect's license cost could be a little lower. But, unfortunately, there aren't many open-source API gateways. Ideally, some new developers could come up with a minimum-functionality open-source solution. When I look for open-source resources that work with API C or Apigee, I find very few that can do that. It's not available or very popular in the open-source community. I've only worked with large companies that are capable of affording these licenses.  A better option for smaller companies might be to have two or three developers build a custom API gateway. That might be more affordable for them.

What other advice do I have?

I rate API Connect seven out of 10. I would recommend it to customers if they have the money to pay for it, but it depends on the ecosystem. So, as a consultant, I would recommend API Connect if the customer already has an IBM license. Big companies generally have IBM middleware running somewhere, so they might have a license for these things. In cases like this, we would usually recommend API Connect for their purposes rather than spending more money on a different product. And if a client is building something entirely new and has to get a new license, we'll compare the options, including Apigee, MuleSoft, API C, or a custom solution. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
KH
Manager Integration Platform Engineering at a insurance company with 10,001+ employees
Real User
Top 5
Offers a good SLA, with technical support available to help, but lacks documentation

Pros and Cons

  • "The solution offers a pretty good SLA."
  • "We've had some issues upgrading to the latest version of the solution."

What is our primary use case?

Right now, our use cases are all internal. It's all API socialization internally. With version 10, we'd like to go externally with an actual API marketplace, however, we haven't gone there yet. 

I don't publish; I manage infrastructure. My role is to implement the infrastructure, maintain it, and enable the developers to leverage the technology.

What is most valuable?

The older versions of the solution were fairly straightforward to install.

The solution offers a pretty good SLA.

We deal a lot with technical support and typically they do help. We need them as we often can't find the documentation that would help us circumvent their services.

What needs improvement?

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.

For how long have I used the solution?

I've been using the solution extensively for at least the last 12 months. We've been working with it since at least 2017. It's been a few years at this point.

What do I think about the scalability of the solution?

Since we're mostly talking about Version 5, which is a very old version, I would have to say that it is not scalable. The memory gets too high and it affects operations. We had to request another server and it cost us money, even when we were doing a migration. Even if we wanted to go to Version 10 we have to still apply what is called a Fix Pack to the old version to have a separate infrastructure.

We have about 100 developers that use the solution currently.

How are customer service and technical support?

We have to go through the levels of support. We open a ticket and then we try to engage. I have contacts that I can go directly to. However, if the documentation was better, we would need to interact with them less.

Which solution did I use previously and why did I switch?

We are currently looking to change over to another vendor.

How was the initial setup?

I actually did the initial setup for Version 5.0 which took a long time to install. It was easier, I think, as we're moving to newer versions. It is due to the fact that we've included Kubernetes and this style of installation that we're doing today which is a little bit more complex. 

The original was not nearly as complex as it is today. 

We're having some issues. If I go from Version 5.0 and I want to upgrade to 2018, I have to request new servers and then migrate all of the APIs. This is the same for Version 10 which wasn't a commitment, however, there was a communication that they would have an upgrade in place by the end of the second quarter and it didn't happen. We spent all 2018 to 2020 installing Version 2018. Now, we're told if we want to go to Version 10, we have to set up new infrastructure.

We tried to do the 2018 installation in three or four weeks and we handled it all in-house.

What was our ROI?

I cannot speak to an ROI.

What's my experience with pricing, setup cost, and licensing?

We have an SLA we can draw from. I need to keep within certain numbers, however, I don't have a problem doing so. I can't speak to exact costs.

Which other solutions did I evaluate?

I haven't had a chance to compare the solution to other products yet, however, the plan is to move away from this product. We still need to do the research.

What other advice do I have?

We are a direct customer and end-user. We aren't a partner of IBM.

We're not using the latest version of the solution right now. We have in production the original version - which I believe is Version 5.0. It was the original version. We worked all those years since 2018 and we're having some challenges to go to Version 10 which is the latest version.

Overall, I would rate the solution at a seven out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Learn what your peers think about IBM API Connect. Get advice and tips from experienced pros sharing their opinions. Updated: October 2021.
541,708 professionals have used our research since 2012.
AdemolaOsindero
CEO at Lopworks Limited
Real User
Top 5
Reduces costs with faster integrations

Pros and Cons

  • "Our version supports containerized integration. I can write APIs, which can be moved into a testing environment without needing a forklift. It can check if APIs are compliant before moving them into production."
  • "There are issues with upgrading in the cloud version. The cloud version is extremely buggy. We prefer to use the on-premise version."

What is our primary use case?

We have implemented this for four or five banks in Nigeria. The bulk of our clients are banks. We need determine if there are transaction capabilities from their back-end applications. If so, then we consume their APIs. For example, we have a logistics company who uses the bank's back-end API to complete their payments.

We specialize in application and cloud integration. 

We have clients deployed on-premise, on the cloud, and with hybrid cloud.

How has it helped my organization?

The workflow allows for different parties to work independently of each other, e.g., business people can work independently of the developers. 

If the rules are well followed and aligned, an organization can run a constant API ecosystem.

Our version supports containerized integration. I can write APIs, which can be moved into a testing environment without needing a forklift. It can check if APIs are compliant before moving them into production. 

API Connects has absolutely helped to reduce the time it takes to deliver new integrations to my clients. Integrations are a lot faster, which is a big selling point, as it reduces cost on the front-end.

What is most valuable?

The developer can connect to the back-end services and exclude APIs through API Connect. It is very robust, e.g., I can exclude web services. We can paste the code into the UI interface.

Pre-built connectors are good if you need more security, though it depends on the extent to which you use them, as they are not necessary to use.

The solution is very simple and straightforward.

What needs improvement?

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. 

For how long have I used the solution?

Since 2017.

What do I think about the stability of the solution?

There are issues with upgrading in the cloud version. The cloud version is extremely buggy. We prefer to use the on-premise version.

What do I think about the scalability of the solution?

It's redundant so scalability is not much of an issue.

How are customer service and technical support?

I would rate their technical support as a five out of 10. They are very slow. IBM has been working on this for three years. 

Which solution did I use previously and why did I switch?

Some of our clients tried to use a customer design. They switched to API Connect because it is more advanced.

How was the initial setup?

The initial setup and development are straightforward. The cloud is already available, so the development is what takes time. Deploying the cloud just takes clicking. It can deployed in minutes. The on-premise deployment takes two or three hours without issues to set up. if there are issues, it could take a day to set up.

What about the implementation team?

It takes one person to set up, max two, as it is straightforward. There is not a lot to do. The system admin will probably spend one to two hours on it to maintain it.

It takes us a week or two to set up 50 services in API Connect. The only thing that might take extra time is portal design because that requires us to go into the back-end.

What's my experience with pricing, setup cost, and licensing?

API Connect is quite pricey.

The developer builds the API and determines what should be put together. However, the business people determine the price.

The product plan and pricing needs improvement. It is confusing to the client based on the way a business might put it together. E.g., I have to be able to pick out different APIs, then group them together. I then have to explain to the client if they subscribe to this API product all the services available. Many clients want a variety of price groups based on their API selection.

I haven't seen anyone go from on-premise to the cloud. In fact, I am seeing people go from the cloud to on-premise because the costs can quickly grow on the cloud. 

If you want to small small, start with the cloud.

Which other solutions did I evaluate?

The integration is quite fast compared to others. Other companies combine their API platforms, but API Connect is as straightforward as you can get it. 

Oracle doesn't understand the different personas that need to be defined. This is why API Connect is superior to it.

Microsoft is extremely cheap compared API Connect. We are reviewing their solution in comparison to API Connect.

What other advice do I have?

The client needs to understand the service to use it. They need to make sure that they have the back-end infrastructure to support API Connect.

API Connect is known for its light front-end system. Therefore, it depends on what system it connects to on the back-end. It is important to know how it connects to the back-end.

We are not using Cloud Pak, as it is still too new. We are using it in the lab.

I would rate the solution as a nine (out of 10). 

Disclosure: My company has a business relationship with this vendor other than being a customer: Business partner.
AR
Lead Architect at a insurance company with 10,001+ employees
Real User
Top 10
Saves us a lot of time and provides a solid structure for anyone wanting to develop an API

Pros and Cons

  • "Security is well organized and managed within the solution."
  • "Different versions of the same thing can mean unnecessary duplication."

What is our primary use case?

Our use case for this solution, depending on the API Connect centralized team, is for registering any APIs. Once those are there, the main idea is that they have to be reusable and available like a global platform rather than just internal to your applications. API Connect does that, you register your API and it is available. Anybody who wants to use that function or that API can now go through API Connect with the current credentials and get access to your API. I'm a lead architect and we are customers of IBM API Connect. 

How has it helped my organization?

This product has provided us with a structured way for anybody who wants to develop any API. It has reduced the amount of time spent on engagement and involvement of the team. They should put it on the cloud and in a mode where anybody can take something like a post run or something and test an API. In that way it saves having to really engage with the source or engage teams. If I want a solution, I can just call API Connect, see that API, test it out myself, and see how it works. Just like an email, there is an API that you can use that can send an email to anybody. I then check how it works and can integrate it with my application. I really don't have to create a work order and go to the team and start engaging them. If it's there you can just started using it. 

What is most valuable?

Reusability is the biggest most valuable feature for us. The security is also a major feature in some ways because if it's in API Connect, the gateway, you're in and out, it's well organized, rather than having some internal solution where somebody has to manage the in and out. In API Connect, the certificates and all those things are managed pretty well. From a security perspective, it makes things easier. 

From an API perspective, it is pretty strong. Again, it all depends on how other teams are implementing like certificates. If you register you eventually have to request certificates which API registers, so it is secure. From that perspective, I think API Connect has a pretty decent product.

What needs improvement?

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.

For how long have I used the solution?

I've been using this solution for three years. 

What do I think about the stability of the solution?

This solution is stable. 

What do I think about the scalability of the solution?

This solution is scalable.

How are customer service and technical support?

The technical support is very good. 

How was the initial setup?

The initial setup is a bit complex regarding what you want to put into API Connect because you're giving to a centralized team that has no idea what API to take and use it for. The centralized team is just a team that has no idea what to collect from these hundred teams. You need to have an idea of what you're taking from them and what they're being used for. That's a bit of a challenge. Again, from a new development perspective, it brings a structural way of development of the future API.

What other advice do I have?

I would definitely recommend trying this product. From a cloud perspective it's there, and from a management of API perspective, all that authentication authorization is quite strong. It's a complete product that you can implement and get a centralized repo of the APIs that you can use enterprise wide. If any other enterprise project comes up, it's worth checking what exists rather than automatically developing from scratch. 

The solution is very easy to use. It's not really complicated, at least for those who are already familiar with some IBM products. We didn't have a problem getting it up and running. 

I would rate this solution a nine out of 10. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Augustine Ayo
Middleware Solution Architect at a tech services company with 51-200 employees
Real User
Top 5
Its dashboard allows us to see where transactions are coming from

Pros and Cons

  • "It is quite stable. We've not had any problem. It has made for a good buy because we are finding that other companies that have similar set ups go down maybe once a month."
  • "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."

What is our primary use case?

We are a financial services provider. We have services that we expose for things like investments, policy management, and so on. We have put this on an API Gateway to be able to aggregate all the things that we do for different types of clients with whom we engage.

What is most valuable?

The exception and error management have been the most valuable feature.  

We take steps for how many transactions we can create. It has a dashboard that allows us to see where transactions are coming from, which clients use it more, etc. This makes it very endearing for us.

What needs improvement?

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.

For how long have I used the solution?

Two years.

What do I think about the stability of the solution?

It is quite stable. We've not had any problem. It has made for a good buy because we are finding that other companies that have similar set ups go down maybe once a month.

Our transactions has been escalating. We're doing an average of about 1.2 million transactions every week now, and it's stable.

What do I think about the scalability of the solution?

We have not tried to scale it. If we go beyond two million transactions a week, we may find more reasons to start exploring scalability.

Right now, we have three clients. The intention is to be able to go to the big investment managers and insurance managers in our sector in South Africa to be able to onboard them. If we have our way, we should have 30 clients, not three.

How are customer service and technical support?

We don't have a dedicated support with them. However, whenever we send an email, we always get a response back, sometime immediately but maximum 48 hours. They have been very quick.

Which solution did I use previously and why did I switch?

Previously what we used to do is deploy different endpoints for different clients that we have onboard. In the last two years, what we've been doing is using API Gateway Manager so we have only one endpoint with different uses.

How was the initial setup?

The setup could be made more simpler. We have had to deploy in three instances. The first one had a huge learning curve, though the second one was easier. We find that if we move environments, it takes time to set up. This should be made simpler. We need to do move our BI environment and we have not done that yet because of the setup time. 

The first deployment took almost five days. Right now, we are averaging around a day or two, then we are up and running.

Which other solutions did I evaluate?

We've played around with other API managers, like Tyk, and the setup is much simpler. 

The reason why we took IBM was because of its resilience and name brand. Our clients trust the fact that we are not just going for an open source or free solution.

One of the key selling points is the easy analytics to be able to analyze what we are getting. We played around with Tyk, but we didn't see any analytics with them. E.g., we tried to connect Tyk to our Microsoft Power BI so we could use that. This feature comes standard with IBM, that's why we're sticking to it.

We have not done extensive checks on Azure because our first client that we onboarded was Google. So, we never really explored Azure that much. In the next six months, we may be exploring Azure so we can have everything in the same space.

What other advice do I have?

To cut down on your implementation time, read the documentation. It's long but explanatory.

I would rate this solution as an eight (out of 10).

Which deployment model are you using for this solution?

Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Ashutosh Aggarwal
Vice President at a comms service provider with 10,001+ employees
Real User
Top 10
Helps with API monetization but needs improvement in design time setup

Pros and Cons

  • "We really like the runtime capabilities of IBM API Connect. The creation of products and the control of the monetization and hit rate are some of the features which we've found very valuable."
  • "The design time setup has a lot of customizable fields, but we need certain standard fields to be added, such as what all of the consuming systems are. This needs to be very clearly articulated during the design time."

What is our primary use case?

It is the go-to solution for API repository products. We use it for runtime by designing certain products, and those products are subscribed to by various consuming systems.

How has it helped my organization?

It has made API monetization quite easy. I can simply log onto the API dashboard and see who has used how much and whether they are using their quota or not. If they go beyond their quota, I can then give them a higher rate. Thus, it has helped us with API monetization.

What is most valuable?

We really like the runtime capabilities of IBM API Connect. The creation of products and the control of the monetization and hit rate are some of the features which we've found very valuable.

What needs improvement?

There are certain areas that need improvement. The first one is the design time setup. It has a lot of customizable fields, but we need certain standard fields to be added, such as what all of the consuming systems are. This needs to be very clearly articulated during the design time.

The second, which was a very big issue for me for adoption, is that they don't give any out-of-the-box solutions for knowing how many users have logged on during the design time and who has access to the portal for how much time. There is no capability right now to tell me the usage details and user rights.

As for additional features, design time user analytics would be great to have in the next release.

For how long have I used the solution?

I've been using this solution for one and a half years.

What do I think about the stability of the solution?

It's quite stable.

What do I think about the scalability of the solution?

Right now, we are using the design time thoroughly, but we are in the nascent stage for the runtime. So we just have a couple of systems using it, but going forward, we have plans for extensive adoption of the runtime capabilities.

Which solution did I use previously and why did I switch?

We were previously using WSRR, and we switched because IBM stopped providing any updates to that product. Also, it was primarily design time only; there was no runtime capability.

How was the initial setup?

The initial setup was a little bit complex because we wanted to put it in a proper Kubernetes cluster. So we had to learn Kubernetes and then do it.

It took us a month to deploy the solution.

What about the implementation team?

We used IBM directly for implementation. We've been using IBM services for the past 13 years, and we are okay with their level of expertise.

What other advice do I have?

I would urge others to use both design time and runtime and not just use it as a repository. I would suggest that they utilize the runtime features, which are pretty strong. First, they can secure your API ecosystem.

Second, they have very good monetizing capabilities, which allow you to design products and see who accesses those products. Usage-based and storage-based restriction capabilities are present, which are probably some of the best on the market today. So, I would really urge people to just go beyond the design time and also utilize API Connect in runtime as well.

On a scale from one to ten, I would rate  IBM API Connect at seven because it is a little bit weak on design time.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
OG
Consultant at a financial services firm with 10,001+ employees
Consultant
Top 10
Robust with an easy initial setup and good stability

Pros and Cons

  • "The interface is very nice. It makes the solution easy to use and navigate."
  • "The documentation needs to be a bit better."

What is our primary use case?

We primarily use the solution for a bank. It's used for the operations portion of the bank. It's primarily used for the review of the personnel in your accounts et cetera. It's for many operations for the bank.

What is most valuable?

The interface is very nice. It makes the solution easy to use and navigate.

You can install it in coordinates, in general, and you can deploy it in Amazon, in Google, in the IBM cloud, or other clouds as well. You don't have to worry about having to work on a specific cloud. It makes it very flexible. This is very important.

The product is quite robust. 

The initial setup is very easy and the deployment is very quick. 

What needs improvement?

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. 

For how long have I used the solution?

I've been using the solution for three years or so. It's been a while. 

What do I think about the stability of the solution?

The stability has been fine. We've found it to be very stable. There are no bugs or glitches. It doesn't crash and freeze. In the past versions, stability was a bit of an issue, however, in the latest version, we have found it to be much better and much more reliable. We are satisfied with it so far. 

What do I think about the scalability of the solution?

The scalability has been good. If a company needs to expand it, it can do so.

We have an average of 1,000 people using the platform normally. On top of that, there are 10 developers that are also on it at any given time. 

How are customer service and technical support?

Technical support could be better. They are so-so. They could be more supportive and be better at answering questions. We'd like it if they made issues easier to resolve.

There's also a general lack of documentation, which sometimes means finding answers on your own is difficult to do. 

How was the initial setup?

The initial setup is not overly difficult or complex. It's very simple and straightforward. 

The deployment is quite quick. It only takes about one hour to have everything up and running. 

What other advice do I have?

I'd recommend the solution to other users and organizations due to the fact that it is very, very easy to use. The product is good, however, that said, they need to pay more attention to their documentation and support. 

Overall, I would rate the solution at an eight out of ten. We have largely been satisfied with the solution and its capabilities.

We are IBM partners.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
HG
Associate Director, Cloud Architect at a computer software company with 5,001-10,000 employees
Real User
Top 10
Stable with good functionalities and works well overall

Pros and Cons

  • "The functionalities on offer are very good."
  • "The solution would be better if it had cloud functionalities."

What is our primary use case?

The solution is primarily used as the API gateway. It's for the application that performs the function as the API for the consumer.

What is most valuable?

The customer seems to really like how this particular solution works.

The solution is very stable.

The functionalities on offer are very good.

What needs improvement?

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.

For how long have I used the solution?

I've only really been assisting my customer, who uses this solution. However, it's my understanding that they have been using the product for a long time.

What do I think about the stability of the solution?

The stability has been very good. It doesn't crash or freeze. There are no bugs. From a performance perspective, it's reliable.

What do I think about the scalability of the solution?

The customer has many, many users on the solution currently. I can't speak to exact numbers. I know there are a lot.

How are customer service and technical support?

I've never dealt with IBM's technical support. I'm unsure if the client even has a contract that allows them access to IBM's support. If they do, I would definitely reach out to discuss the product and its capabilities more. I'm not sure if a technical support license is extra or just comes with the license itself or if it expires over time, et cetera. I haven't looked into it at all.

How was the initial setup?

I've never handled an installation before. I wouldn't be able to speak from personal experience. I can't get into details about implementation or deployment or how long the process takes.

Which other solutions did I evaluate?

I proposed to the client that they use the cloud-native API gateway in Azure or in AWS, however, they wanted to go for the API Connect.

What other advice do I have?

I'm considering migrating API Connect to Azure.

I'm still doing the assessment for this product. That is due to the fact that the move to the cloud is just not only for this product. We have a lot of products in terms of the customer's applications. I need to assess everything together and then propose to my end customer.

I'm a vendor. I do assessments for my customer.

I wouldn't recommend this solution to other organizations at this time. It's on-premises and everyone is moving to the cloud. It makes more sense to seek out a cloud solution.

Overall, I would rate the solution at an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
Buyer's Guide
Download our free IBM API Connect Report and get advice and tips from experienced pros sharing their opinions.