What is our primary use case?
We use it along with IdentityServer, as our main API management tool for API exposure to the internet. It's not for internal usage, it's for external use.
What is most valuable?
The main feature — the publication of the API, the management section — is great in general.
What needs improvement?
I think it would be very unfair for me to answer this question because we are running a very outdated system (they might have improved it a lot with their newer versions), but I'm going to try it anyway. I think they could greatly improve the general UX with their solutions because when you manage different components that are meant to work together, it's very difficult. You have to deal with two completely unrelated interfaces.
Perhaps they should include a tool to assist with migrating to Azure.
For how long have I used the solution?
I have been using WSO2 API Manager for the past four to five years.
What do I think about the stability of the solution?
Stability-wise, it's actually pretty nice — it's good. I wouldn't say it's very good or excellent, but it's good. It fits the bill.
What do I think about the scalability of the solution?
Scalability-wise, I'd give it a three-star rating out of five — good, but not very good or perfect.
The provisioning has to be done manually. In terms of system-wise configurations, these settings involve a lot of big Java components, so it's not natural. It's not very easy to handle. Again, this is an older version. Perhaps they have already worked on this.
How are customer service and technical support?
We don't have a contract for dedicated support. We have to deal with internet forums, etc. Officially speaking, there's no support outside of community forums.
The documentation and community support are pretty helpful. There are a lot of questions answered about WSO2 on several forums and message boards, etc. Although it's not dedicated, it's quite relevant.
Which solution did I use previously and why did I switch?
We're actually in the process of switching to Microsoft Azure API management.
For us, the main benefit of Azure is that it's a managed solution. We have a very restricted theme and not having to deal with the actual configuration of the platform or the underlying operating system and other intrinsic administration tasks is a big win for us. The feature that we use the most and that is most licensed is perhaps the online portal. The certified online portal is the biggest win for us because we can deal with the associated integrations within this new portal, which we can't in the current stack, the on-premises stack.
How was the initial setup?
I wasn't a part of the original project, but I know that the initial setup wasn't easy.
What's my experience with pricing, setup cost, and licensing?
We use the open-source version — the free version.
What other advice do I have?
I wouldn't actually recommend this to anyone. I think that there are paid solutions, such as Azure API Management, which will relieve you from the administrative burden. Personally, I wouldn't recommend this solution at all.
On a scale from one to ten, I would give WSO2 a rating of seven. It's a good tool, but dealing with the on-premises infrastructure is a big headache.
Which deployment model are you using for this solution?
Which version of this solution are you currently using?