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

WSO2 API Manager OverviewUNIXBusinessApplication

WSO2 API Manager is the #6 ranked solution in our list of top API Management tools. It is most often compared to Kong Enterprise: WSO2 API Manager vs Kong Enterprise

What is WSO2 API Manager?

WSO2 API Manager is an open source approach that addresses full API lifecycle management, monetization, and policy enforcement. It allows extensibility and customization, and ensures freedom from lock-in.

WSO2 API Manager is a unique open approach to full lifecycle API development, integration and management. As part of the larger WSO2 Integration Agile Platform, it is a central component used to deploy and manage API-driven ecosystems. It’s hybrid integration capabilities further simplify projects that span traditional as well as microservice environments. And unlike other API and lifecycle management products, it is fully open-source allowing for extensibility and customization.

WSO2 API Manager Buyer's Guide

Download the WSO2 API Manager Buyer's Guide including reviews and more. Updated: September 2021

WSO2 API Manager Customers

StubHub, Dialog

WSO2 API Manager Video

Pricing Advice

What users are saying about WSO2 API Manager pricing:
  • "We have not opted for the paid version of WSO2 but we have implemented the free and open source WSO2 software to a great extent and it is working as per our expectation."
  • "There is a subscription-based pricing structure and also the open-sourced version available."
  • "We use the open-source version — the free version."

WSO2 API Manager 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
PrashansaShukla
Software Engineer at Jio Platforms Limited
Real User
Top 10
Easy to adopt and lets us extend functionality at any time

Pros and Cons

  • "One of the great things about WSO2 API Manager is that it is so easy to adopt. And because it's an open source solution, we're able to extend the implementation any time to suit our company needs better."
  • "From a product perspective, the first thing is that although the documentation provided by WSO2 is good, it could be much better. We're in the middle of a complex migration, moving away from VMs to Kubernetes with the latest version of WSO2 and good documentation is essential to us right now."

What is our primary use case?

I work as a software engineer on the WSO2 API management and WSO2 identity and access server, using version 2.6.

At my company, Jio India, I have been one of the main people driving adoption of WSO2. In the beginning, we used WSO2 on virtual machines to handle the API and IAM requirements for more than 40 applications. Now we are currently in the process of migrating to WSO2 version 3 with Kubernetes as our orchestration system.

How has it helped my organization?

It has helped us manage and scale our APIs in one solution, which is important to us as a large enterprise with over 40 applications relying on various APIs.

What is most valuable?

One of the great things about WSO2 API Manager is that it is so easy to adopt. And because it's an open source solution, we're able to extend the implementation any time to suit our applications better.

What needs improvement?

From a product perspective, the first thing is that although the documentation provided by WSO2 is good, it could be much better. We're in the middle of a complex migration, moving away from VMs to Kubernetes with the latest version of WSO2 and good documentation is essential to us right now.

If you are doing some basic implementation, that's easy enough to do with the current documentation, but suppose you are stuck with an error or you're engineering a complex scenario. In this case, when diving deep into the documentation, it's very helpful to find more information on how things are connected, what each file does, and what the various configuration settings do.

Although they do have paid support which may help in cases where documentation is lacking, we aren't paying for a support license at the moment so we would definitely like to see better documentation for those in our kind of situation. Especially since we're using WSO2 API Manager to such a large extent.

Beyond documentation, they have provided a caching mechanism which I believe could also use some improvement. Once you have set up and implemented WSO2, caching becomes very important and I think they could work on the cache parameters, etc., to make it easier to work with.

Regarding the code itself, there are some bugs which we have encountered among the many different enterprise-level scenarios we have faced. Once again, because we are not paying for the licensed version, it becomes more difficult to request changes and bug fixes to the WSO2 codebase. So, for example, when we find a bug, we would like to be able go to GitHub and get better help on creating a solution that we can quickly push into production.

For how long have I used the solution?

I have been using WSO2 API Manager for about five years now.

What do I think about the stability of the solution?

Apart from some bugs which can be expected in a complex enterprise environment like ours, it is a stable product. 

What do I think about the scalability of the solution?

In terms of orchestration, it's very scalable. Especially when using Kubernetes to handle the orchestration. When we are creating our deployment architecture, we can easily define all sorts of parameters. For example, we can change the CPU parameter, memory parameter, etc., as needed.

How are customer service and technical support?

We don't have a license with WSO2 so I couldn't connect with the WSO2 team for technical support. I was the main engineer who drove adoption of it at my company, and during initial setup, editing of the product, and implementation, I obtained a lot of support from Stack Overflow, LinkedIn WSO2 groups, Slack conversations, and GitHub.

How was the initial setup?

From a deployment perspective, initially, we had started with our deployment on VMs (virtual machines), which we understood would take some time to get right. Thankfully, WSO2 provided many sane defaults in the initial setup, including defaults for authentication and so forth, which saved us some time.

But as we migrated our deployment from virtual machines to orchestration using Kubernetes, it became a bit more complex. It took us a long time to figure out the best way to configure the orchestration, since there are multiple ways of doing it with Kubernetes. Another complicating factor in the orchestration setup is that we have to always keep in mind where our users are located, so that there won't be any negative impact on their end.

Keeping all these points in mind, we finalized deployment by creating our own API manager image which we could deploy in Kubernetes. This image was based on our previous VM setup, which we simply reused. However, it was still a challenging task to get everything correctly configured for the Kubernetes orchestration, especially since we were in the middle of simultaneously migrating 15 different implementations.

Now that we have mostly finalized the deployment architecture for our APIs, it's much easier moving forward. We know exactly how to deploy the base image, and there's not much work to do now except for changing parameters around and so on.

What about the implementation team?

We are implementing WSO2 API Manager without any paid support licenses so we do mostly everything in-house.

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

We have not opted for the paid version of WSO2 but we have implemented the free and open source WSO2 software to a great extent and it is working as per our expectation.

Which other solutions did I evaluate?

When we started looking into it, we compared WSO2 products with a few other products including MuleSoft, Tyk, Kong, Nginx, and Express Gateway. Obviously each product has some pros and cons, but out of those products, we liked WSO2 and KONG. Again, both have their limitations, but as an enterprise business we found WSO2 more easy to adopt.

What other advice do I have?

WSO2 API Manager is a good solution for enterprise API management and, even better, it is free to use the software. If you are doing complex implementations, however, it might benefit you to go with a paid license which will help when you discover any bugs or need extra support that the documentation cannot provide.

I would rate WSO2 API Manager an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
SS
Business&Integration Arch Manager at a tech services company with 201-500 employees
Real User
Top 5Leaderboard
Open-source solution that's fully containerized and easy to scale

Pros and Cons

  • "The solution is open-source."
  • "The stability is pretty good, but it could be improved."

What is our primary use case?

One of the main use cases for our organization is that we can use it as a digital integration hub. You can also use it as a base for a marketplace or open banking.

We are using it for the enablement of a digital service or digital integration hub. We are helping small customers to digitalize their services. We select the best of these services and solutions and trying to deploy them in our platform and expose them to several different clients.

What is most valuable?

The solution is open-source.

The main feature that I like the most is that it is a containerized solution. The API solution is fully containerized. It also has a micro-gateway.

You can scale the solution up and down easily. It's not a monolith. It's a containerized solution. It's an important and strong feature. It's fully flexible.

The solution has a stack and different products that fit well to my requirements, such as a micro-integrator, analytics, streaming integration, and identity access management.

What needs improvement?

I'm using the open-source version, therefore my comments are basically related to just the open-source version. I specify this, due to the fact that, if you have a subscription, you can have access to enterprise support. I need to work within the open-source community to get answers. When I deal with the stack overflow, it's a complex item that could easily be addressed by technical support, and yet, I don't have access to them on my current system. It would be helpful if the solution offered more communication about their technology and services. It would be useful for those of us on the open-source option.

Since the product is updated periodically there are lots of provisions. The documentation could be stronger and maybe the community support could be stronger. I don't have the luxury of turning to their in-house technical support to help me troubleshoot. I'm reliant on documentation and the community.

The stability is pretty good, but it could be improved.

It would be ideal, for our purposes, if the solution offered GraphQL support for the micro-gateway.

For how long have I used the solution?

I haven't been using the solution for too long. It may be about six months at this point.

What do I think about the stability of the solution?

The stability is pretty good. I'd rate it at four out of five. We didn't encounter intermittent issues and as long as you tailer your architecture or deployment pattern according to your project requirements you will not have lots of issues.

What do I think about the scalability of the solution?

The solution scales really well as it is containerized. You can easily add more containers and built it out as much as you need to, or take them away and scale down. It's very easy to accomplish.

We have about 20 people using the solution currently.

How are customer service and technical support?

We don't have access to technical support as we are using the open-source version. We need to rely on documentation and the community to help us troubleshoot.

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

Before using this solution I used Apigee. I chose this product over Apigee due to the fact that I could start with an open-source version. It was an advantage. My preference was choosing open-source. 

I know that Apigee has stronger capabilities, however, I want everything going to open-source solutions. Also, this solution has other components such as the micro integrator, access management, and other capabilities that were appealing. You can easily integrate with the API manager as well. There were just a lot of up-sides to making the switch.

How was the initial setup?

The solution is not complex to implement. It's straight forward. You have access to charts and you have templates for different deployment patterns that you can follw. It's very easy to deploy. 

You can really tailor your installation, depending on your own requirements. The complexity comes from the project being deployed and not the product itself. In our case, we don't have any complexity, and therefore it was easy to install and deploy.

If you are just using a template, you can deploy the solution in less than one hour. After that, you need customization and configuration to happen. That will take some time. The running version of this software was almost one week for our scenario. Then for the API manager to do their work, I can say it will take less than one week.

You only need about three senior developers for maintenance purposes. Currently, we are working with one architect and two engineers for maintenance activities.

What about the implementation team?

I handled the implementation myself. I didn't need the assistance of a consultant or integrator.

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

If you are using open-source, it's not expensive. If you choose to upgrade to get enterprise support, then you need a subscription and it has a cost. I am not using the enterprise support and I don't have a subscription. Therefore, I'm not technically paying for the product at all.

What other advice do I have?

We're just customers. We don't have a business relationship with the company.

I'm currently using the open-source version of the solution. We're evaluating 3.2.0.

On a scale from one to ten, I would rate it at an eight. If it offered better stability and more documentation, I'd rate it a bit higher.

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.
Learn what your peers think about WSO2 API Manager. Get advice and tips from experienced pros sharing their opinions. Updated: September 2021.
541,462 professionals have used our research since 2012.
RiteshShah
Vice President at Exzatech Consulting And Services Pvt Ltd.
Real User
Top 5Leaderboard
WSO2 API Manager for Enterprise Digital Transformation

Pros and Cons

  • "Helped us to quickly publish our Microservice APIs and enforcing different policies against them, it comes up with features like Security, Throttling policy and it provides complete access to customize API's which actually saves development effort and time."
  • "Providing easy configuration for email and SMS notifications, layout and customization of admin and developer landing pages."

What is our primary use case?

We have developed a slew of applications for Bank, that helped transform multiple core banking processes, such as customer onboarding, account servicing, and rapid loan request fulfillment. The solution, which is powered by WSO2’s API management and enterprise integration technologies, seamlessly bridges systems while paving the digital path to a connected financial ecosystem.

How has it helped my organization?

  • Reduced operating costs by using open-source technology solutions
  • Enhanced customer trust built through multi-channel communication
  • Shortened delivery time for client services
  • Improved compliance and reduced risk exposure

What is most valuable?

Helped us to quickly publish our Microservice APIs and enforcing different policies against them, it comes up with features like Security, Throttling policy and it provides complete access to customize API's which actually saves development effort and time.

The solution offers a simple and easy configuration. You can get it working up within one or two days' time. It's very fast, simple to use, and you can deploy things quickly. Its very easy to configure and takes less time to create customize policies across the API Gateway.  

The solution is very stable and can scale well.

What needs improvement?

Providing easy configuration for email and SMS notifications, layout and customization of admin and developer landing pages.

For how long have I used the solution?

We've been using this solution for last 5 years.

What do I think about the stability of the solution?

It's stable. There is no issue with it in that sense at all. That said, some of the customers who have faced issues have had problems in the updating part. For example, when they update something, something goes wrong. However, if they are following a proper process, they should be okay. Whenever you have to do an upgrade you should first do it in a staging environment to test it and make sure you won't have issues. If everything works properly there only then should you move into production. If somebody follows a proper IT process, then they will have no issues. We have never faced any issues and it's a perfectly stable platform as far as we are concerned.

What do I think about the scalability of the solution?

WSO2 API Management platform can be deployed in a scalable manner where the system can handle 1000RPS with 10 - 20 KB payloads.
WSO2 API Manager can be deployed in a way where auto scaling is there so whenever there is a traffic spike the deployment can auto scale.
Also, APIs can be deployed across multiple gateways so one APIs traffic spike won't affect the rest of the gateways.

How are customer service and technical support?

Tech support is very good. The open-source version means you have to get support from the community. However, if you have a subscription, they provide the support portal and everything is solved there. Therefore you get support directly from the project team. The engineers who developed the product directly support you sometimes and you get very good support from them. 

There are no issues with support at all. Even if you need some sort of customized help, the engineers will assist. It's very helpful.

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

have used 3scale earlier, to lower costs, simplify maintenance, and because WSO2 API Manager is open-source

How was the initial setup?

The initial setup is not complex or overly difficult. In fact, it's pretty straightforward. The solution offers a simple and easy configuration. You can get it up and running within one or two days. The deployment doesn't take very long.

We have implemented both all-in-one deployments and distributed setup. The distributed setup is a little more complex, most of the time takes in network configurations. That said, the basic setup is very simple and fast.

What about the implementation team?

We have a dedicated lab setup for trying new features, and we provide implementation and support solution to our customers.

What was our ROI?

Complete feature set in the open source version

Flexibility and extensibility

Complete platform with built-in integration and security

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

Single GA (generally available) edition with all features. Subscription model

Simple pricing model with per core pricing. No licensing fees for development

Each subscription also covers, at no extra fee:

• Bursting of on-premise production systems by up to two times the subscribed cores, lasting for up to 3 cumulative days during the subscription year.

• Up to 3 pre-production environments

• Individual development machines, though please note that issues arising on such systems qualify for query support rather than incident support SLAs

• Analytics Profiles

• Passive instances in an active/passive deployment

• Disaster recovery systems

• Query support hours up to a level proportional to the subscription fee

Which other solutions did I evaluate?

We evaluated 3scale, Apigee and Tibco

What other advice do I have?

I'd rate the solution at a ten out of ten. We've been extremely happy with it so far. It's affordable and pretty easy to use overall.

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
Modupe Aladeojebi
Chief Technology Officer at Swifta Systems and Services
Real User
Top 20
Easy setup and stable

Pros and Cons

  • "Most of the time, we need to install a plug-in without having any lapse in services or restarting the application. The WSO2 platform can do all deployments without any downtime."
  • "I can say that user management is not really flexible. So, if I want to create 1,000 store users, I can't do it as a publisher. You have to register as a store user using the store URL."

What is our primary use case?

Our normal use case for API Manager is to create pre-configured store users. The administrator who creates those users then sends them their credentials and secure links.  We are running API Manager on a Tomcat server. Currently, I am the main person who works with API Manager, because it requires a proper understanding of the APIs. 

How has it helped my organization?

When looking at things from an enterprise point of view, it's often difficult to see the benefit of a tool. Most of the time, we need to install a plug-in without having any lapse in services or restarting the application. The WSO2 platform can do all deployments without any downtime.

What is most valuable?

API Manager upgraded to 3.2 recently, and it has more flexibility in terms of authentication methods. In the version we're currently using, there is only a token. We couldn't do basic authentication.

What needs improvement?

In version 2.5, there is room for improvement on the UI. That may have been addressed in the upgrade to 3.2, which uses the latest front-end framework that's commonly used in other solutions like JIRA. I would need to play around with the upgrade, but I believe the UI issue has been addressed. I can only speak about my experience with the 2.5 version because that's the one I've been able to use extensively. I can say that user management is not really flexible. So, if I want to create 1,000 store users, I can't do it as a publisher. You have to register as a store user using the store URL. It would be nice if API Manager had that functionality as an administrator, so you would have a user management interface where you can create store users.  

For how long have I used the solution?

I've been using API Manager for more than five years. I was using the platform before the recent overhaul. They now have this new interface where they migrated the front end to using view. So I think view framework or react, one of the two, but it's been a while.

What do I think about the stability of the solution?

API Manager is stable. We haven't had any stability issues at all. It has run on Tomcat for as long as I know, and it's a stable web service so.

What do I think about the scalability of the solution?

In terms of scalability, it has so far been able to handle the traffic on the platform. We haven't had any issues where we've had downtime because too many requests were coming in per second.

How was the initial setup?

The setup was pretty straightforward. I asked my colleague to do the setup. Since I've been working on it for a while, it probably wouldn't be a challenge. We didn't use many resources to do the setup or spend much time setting up the application because they've added more deployment scripts to make the solution easier to deploy.

Which other solutions did I evaluate?

Maybe I lack the curiosity to push me to check other platforms. Even when I try checking them, I've not actually checked other competitors because the major competitor got acquired by another platform.

What other advice do I have?

I would rate API Manager eight out of 10. The advice I would give to anyone considering API Manager is to take the time to understand how the platform works. It doesn't matter how good a thing is if you don't understand the purpose. For example, you need to understand the use case for service orchestration. And once you know that, you know why it makes sense to bring in WSO2 API Manager. This is a better way to go about things than to force yourself into it, only to find out that it's not working for you at the end of the day. 

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.
Flag as inappropriate
AR
Project Manager at a tech services company with 51-200 employees
Real User
Top 20
Easy API lifecycle management, simple deployment and install, with great support

Pros and Cons

  • "As far as I am aware this solution is the first API Publisher that allows you to create and publish API and to manage the API lifecycle."
  • "From what I have experienced from the versions I have tried, they could improve on the multi-tenant environments to allow some kind of SSO single sign-on between tenant."

What is most valuable?

As far as I am aware this solution is the first API Publisher that allows you to create and publish API and to manage the API lifecycle. It is very simple to manage an API lifecycle in this platform. Another great feature is the API store. It has the built-in test features, that allows the API creator to document their API and then publish it. The developers can go to the store and see the API, see the documentation, and can try the features. This is great for developers to have an easy way to test the API before using it. These are the best features I have experienced.

What needs improvement?

I have been using the older version of the solution and they have made a lot of changes in the newer versions. I tried version 3.2 and it is easier to navigate the APIs and even to manage the API. From what I have experienced from the versions I have tried, they could improve on the multi-tenant environments to allow some kind of SSO single sign-on between tenant. This is one great way to improve this product.

For how long have I used the solution?

I have been using the solution for approximately two years.

What do I think about the stability of the solution?

It is a stable solution. However, the main issue is, if you are working with the open-source version, sometimes depending on the version, you need to deal with some issues and bugs. Usually, they are working fine but their business model is if they release a version and they find bugs, they will release another version fairly quickly with the fix. This means, if you do not have a subscription, for example, you are using version 2.6 and it has bugs, you will need to correct the bug by yourself or you need to wait to the next release.

How are customer service and technical support?

The customer service is helpful. If we have any kind of questions regarding improvements or bug fix. We can open a ticket for the direct support and be connected to the support team, it was great.

How was the initial setup?

The installation is very straightforward because you have multiple ways to do the setup. For example, if you are trying it, you can just download the product and click on the setup script, and it will be load up with the MIMO configuration. In production environments, you can use something like Kubernetes and it is also easy to do the deployment. They have features to connect to external user stores. This is great too, you can choose any kind of database you need and the start-up is easy. Even if you want to develop on your computer, you could download a script. The setup has all the configurations and with one command you can run multiple products at the same time.

What about the implementation team?

Deployment is simple all you do is download the solution, click, and it is up and running. For production deployments, you will need less than a day for a simple setup working with Docker or something similar. If you are going to use Kubernetes, I think it mainly depends on your know-how on how to use Kubernetes itself. This solution is a very quick setup, there are not too many things to deal with.

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

There is a subscription-based pricing structure and also the open-sourced version available.

What other advice do I have?

You have two options to choose when deciding what type of version you want to go with, the open-source or the subscription version. In a production environment, it is best to go with the subscription to make sure all the bugs are fixed.

I recommend this solution to others.

I rate WSO2 API Manager a nine 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
Leonardo Ferreira
Software Architecture Leader at Edenred
Real User
Top 10
Great API management, but there are better solutions available

Pros and Cons

  • "The main feature — the publication of the API, the management section — is great in general."
  • "I think they could greatly improve the general UX with their solutions."

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.

We have two main roles regarding WSO2 API Manager. There are the admins, who publish guides and user updates, etc — we employ around four people who perform this role. In terms of users, we have around five to six million users going through it on a monthly basis.

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?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Andrés Pastorini
IT Solutions Architect at Agesic
Real User
Top 10
Provides all the required tools for a management solution.

Pros and Cons

  • "There are a lot of tools to help the manager. WSO2 is very easy to install. It has all the principal functionalities that you think about when you want to put up the management solution. It's a very friendly tool."
  • "I would like it to be a more stable solution. Maybe in the last version that is approved. For me it would be good if they had a community established version."

What is our primary use case?

The principal things we use WSO2 API Manager for are to convert SOAP to Rest services, add security, and to provide more function for the administrators and to the developers. These are the main items.

We now work with two versions which are in a test environment. We are using version 3.0 and version 3.2. It's very possible that the version that we will use in production will be 3.2.

We can use WSO2 API Manager at IaaS and PaaS enviroments.

What is most valuable?

 WSO2 is very easy to install. It has all the main functionalities that we looking for when we want to put up the management solution like a friendly UI tool, soap to rest API publication options, plugin extensions, add oatuh 2.0 to the operations,  install on premise, hablde multiple versions of the same api, import and export swagger. 

What needs improvement?

In terms of what can be improved, we are doing a proof of concept and we found some problems with the migration process from the last version to the 3.2. We have problems with the migration of the tenants.

For how long have I used the solution?

I have been using WSO2 API Manager for about one and a half years.

What do I think about the stability of the solution?

In terms of stability, we are testing it in the test environment now so I don't have information about this. Maybe in the future we will know better.

What do I think about the scalability of the solution?

In terms of scalability, it has several main components and it is easy to make different strategies with each one. For example, we can deploy one component in high availability and you can use a different strategy with others components of the tool.

We now have around 10 people using it because we are working in the test environment. In the future, we expect different organizations use it too.

For now, we want to put a community version in production, test it, and then analize if it is an option to switch to commercial. 

How are customer service and technical support?

In terms of the technical support, we don't use it. But I would evaluate documentation manuals as very good.

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

We made POCs with ApiConnect, and 3scale.

For example, 3scale has a very good user interface but it's doesnt has the functionalities that we need. ApiConnect is similar to the WSO2 but it's more expensive. WSO2 API Manager is easier to start with.

How was the initial setup?

The initial setup is very easy.

I did not do the deployment myself but I think that it took around one or two hours. No more than this. This is because we need a different database. We needed to change something in the default, but otherwise it was very easy.

What about the implementation team?

We contracted an external worker that did these things on the monitor.

 We are happy with the tool. Now, we need to do more test. We started one and a half years ago, or more and now, we can solve the evolution of the two different versions.

What other advice do I have?

Improve the possibility to migrate to different versions would be very good. It would also be good for integration withdifferents identity server to have more possibilities with other tools. 

On a scale of one to ten I would rate WSO2 API Manager an 8 because I think that the evolution of the product has a lot of differences between near versions. I would like it to be a more stable 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.
Xinxiao Li
Chief Specialist at a manufacturing company with 10,001+ employees
Real User
Top 10
Unifies our microservice and then publishes the service outside

Pros and Cons

  • "The most interesting feature is its Mac-based function."
  • "API Manager is not easy to scale because some of its components lack scalability. It's a difficult point. Especially because companies are so cloud-based these days, microservice scalability is a major thing."

What is our primary use case?

We use API Manager to publish our microservice for the public. We also use it because of its integrated functionality. We are researching many kinds of functions with WSO2, not only WSO2 management.

What is most valuable?

The most interesting feature is its Mac-based function. We want to use the API Manager to unify our microservice and then publish the service outside. In the future we want to combine it with our service. But we haven't implemented it for other Mac-based work, yet. This is an interesting element.

What needs improvement?

WSO2 API Manager is a little complex to use. I think the user interface could be improved. 

Additionally, the installation setup is a little complex. I think in future versions I would like to see some improvements in the system's installation.

For how long have I used the solution?

I have been using WSO2 API Manager for about half a year.

What do I think about the stability of the solution?

We deployed directly to the API Manager, and when we tested the performance we got a memory error. I don't know where or how to solve it. Maybe the memory size, or other setup parameters can solve this problem. I'm not sure whether it's an issue of stability, but it's an issue. We think this problem can be solved by many methods. Fundamentally, the problem is a general memory problem, not necessarily a WSO2 API Manager problem.

We are discussing use keys in our organization. Maybe some end user will come for testing and we can fully deploy the API Manager to be used every day.

What do I think about the scalability of the solution?

API Manager is not easy to scale because some of its components lack scalability. It's a difficult point. Especially because companies are so cloud-based these days, microservice scalability is a major thing.

How are customer service and technical support?

We have only contacted support two times.

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

We did discuss several different options but we liked WSO2 API Manager because it is an open source system. So we think it's better for our current needs.

How was the initial setup?

The initial setup is not easy. There are many different components which need to be coordinated. The way that you receive the public's message interface is very complex.

Initial setup took two or three weeks the first time. It's not a perfect system or setup.

We had two people working on the installation but not full time.

What about the implementation team?

We installed the system by ourselves.

What other advice do I have?

I recommend this product. I think WSO2 API Manager is good. I'd like to recommend the system to others.

On a scale of one to ten I would rate WSO2 API Manager an eight.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Product Categories
API Management
Buyer's Guide
Download our free WSO2 API Manager Report and get advice and tips from experienced pros sharing their opinions.