What is our primary use case?
We use it for API management, as an API gateway. All those APIs have been published there, and we call them from there. It's a centralized platform.
So, overall, it's used as an API gateway and for publishing APIs. This is a bit like a custom-built solution. So, it is specific to the customer. It is like a customer portal, like internet-facing.
Currently, we do have it in our application portfolio. But in the future, we're trying to replace it due to organizational guidelines to move away from certain prices and costs.
How has it helped my organization?
What is most valuable?
It has something called packages. In that way, it's good because we have some pre-built packages. So, if you want to onboard different APIs, we can just add them to the package, and it's there.
But when you want to do some fine-grained configuration, it fails. Overall, when I try to onboard something, it's quick because of the packages. But with the fine-grained configurations, we face some issues.
What needs improvement?
The configuration is not that easy.
It's not that user-friendly, and security-wise when you try to implement the security layer on top of it, it's not that easy either.
There are certain things where the performance is not that great. When the traffic is huge, we see some lag in performance.
For how long have I used the solution?
It's been in the organization for a long time, but I've been here for the last five to six years. I've been using it for the last couple of years.
How are customer service and support?
Support is okay, sort of. They respond back, but sometimes it lags a bit.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I have some protocol exposure to Apigee. Apigee is well integrated with Google Cloud Platform (GCP). If you have GCP, it gives you a better way of handling things because Apigee has some inbuilt facilities that work well with GCP. Also, for AWS, they have their own API gateway.
In that way, there are certain things like the name build, which you can utilize quickly and don't need to create plumbing code to make it work. So, the integration is easy.
How was the initial setup?
The setup was done a long time ago.
It requires maintenance. Sometimes, we face issues regarding performance. We talk to the support team and try to figure out the issue.
Also, the security layer is not configured in an easy way, so we face some issues. For those sorts of things, we get support.
What was our ROI?
It provides a centralized way to configure security and other things. It's not a direct cost saving, but if you consider the potential issues caused by a security breach, this is a better way of providing centralized control. In that way, it is an ROI.
The overall impression is okay.
What's my experience with pricing, setup cost, and licensing?
My primary role was to assess the solution from a capability perspective. So, there are some issues with the licensing cost.
What other advice do I have?
Overall, I would rate the solution an eight out of ten.
*Disclosure: My company has a business relationship with this vendor other than being a customer: Partner