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?
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?
Which version of this solution are you currently using?