WSO2 API Manager Reviews

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.

 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. 

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.

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

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.

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. 

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

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.

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.

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.

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. 

I have used features like routing and authentication, as well as the most well-known features of WSO2.

WSO2 API Manager has some support problems and can be a little complex.  So our developer teams decided to use 3scale or Kong instead. We found WSO2 API Manager to be a bit complex.

So, in terms of complexity, WSO2 API Manager has some challenges. Also, there is a bit of an issue with the pricing and license of WSO2. It's a little high.

I used WSO2 API Manager for two projects. However, I can't say I have used it all the time. I have about 50% experience and knowledge about it.

We are not satisfied with the customer service and support. In a few instances, their response time has been a bit slow.

Neutral

It is difficult to implement WSO2. The implementation can vary depending on various factors, such as the features required and the availability of human resources, including developers. It could take anywhere from two to three months or even just one week, depending on the specific requirements.

Our team worked together with our developers to carry out the implementation.

For our projects, we found it to be a little high. However, it may not be the case for another company or project. Because the costs depend on the specific features you would require and other factors.

It's a good product. I prefer it. However, I would only recommend using WSO2 API Manager if the user has a specific requirement for one of its features. If they don't have a specific reason for using it, I can't provide a recommendation because it depends on factors such as the project, the local team, and the desired features. The API management system is complex by default. Therefore, the selection primarily depends on the project and the programming platform used by the developers.

Overall, I would rate WSO2 API Manager a seven out of ten because there is still room for improvement. 

I use the solution in my company as an enterprise application that will be placed in more than 175 places across the world, which would be in different countries. As an API management tool, it will be placed across different regions on Azure Cloud and WSO2's cloud.

I work for the front-end applications in my company, for which we consume APIs with the help of WSO2 since it is also used in our multiple different back-end systems, causing the tool to get integrated and work as a middle layer in our organization.

WSO2 team recommends mTLS as security. Recently, my company faced some issues when implementing mTLS between the DB and front-end applications. My company needs Technical help from WSO2's team to deal with the aforementioned area. WSO2 team should provide better guidance in documentations to implement this.

I have been using WSO2 API Manager for a year.

It is possible to scale up and scale down with the solution. As my company is involved in the setup of the product in different regions, I can say that I have not seen any issues related to scalability.

I have contacted the product's support team, and my company gets support on time since we have enterprise-level support from WSO2 since we are involved in a big project. My company raises our concerns about the product with the support team through an available ticketing system. My company can also call the product support team directly.

I rate the technical support an eight out of ten.

Positive

I have previous experience with Azure API Management and Apigee API Management.

It is wrong for me to compare WSO2 API Manager with the tools like Apigee API Management or Azure API Management that I have used in the past since they may have matured a lot during the time frame when I have not used them over a period of a year. I cannot compare the product I used in the present with the product that I used two years ago. On a quarterly or six-month basis, many tools get upgraded.

There is a separate team in our company to take care of the tool's setup phase. I work as an architect and have experience with the setup phase of Apigee. I mostly focus on the front-end applications in our company.

My company has to operate in different regions, which are spread out in 175 places across the globe. My company soon plans to set up the product on the cloud platform for different regions, primarily with the services from Azure Cloud for regions like the USA, India, the Gulf, and China. For every region, my company needs to deploy the product separately. The DevOps team has set up the product in various regions for my company.

The solution is deployed on the cloud.

My company chose WSO2 API Manager based on the decision made by the client who wanted it in their environment.

My company is okay with the analytics and usage of the product. The analytics part is mostly managed by the client who uses the product or the API team in my company, so I am unsure about the analytics part.

My company has used the product's customized integration capabilities for MongoDB and some other commercial tools.

Speaking about the most beneficial features for API lifecycle management, I would say that my company has a DevOps tool in place for deploying all the APIs. My company also received feedback from WSO2's team during the development phase. On the API lifecycle management side, I do not see much, but I know that it consists of areas like API versioning and API deployment. I don't see anything special when it comes to the API lifecycle management area of the product since it is similar to what AWS offers. All the processes related to the product are taken care of by my company.

I have worked with many API management tools in the past, and I don't see any case scenarios that were different from what I have seen while using other products.

My company has faced so many technical challenges in many areas. Our company's team members face issues with the product since we have not yet properly implemented it. I have worked with the API management tool from Google in the past and have seen that Google provides better documentation, which is much better and cleaner than what WSO2 API Manager provides.

I rate the overall product a seven out of ten.

We use WSO2 API Manager for securing API calls for various applications.

WSO2 API Manager is easy to use.

I would improve the product documentation. There are some gaps, and it can be difficult to find the proper documentation for the product if you need to solve something.

There are some new features, but we are not currently using the most recent version. We're looking forward to the new release.

The initial setup could be simplified.

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

We have a subcontractor who occasionally downloads new versions from the repository and dates them on a half-year basis.

It is not scalable, in a specific way, but scalable in OCP.

There are 20 to 40 applications and thousands of users who are working through the solution.

We are quite satisfied with technical support. 

I would rate technical support a four out of five.

Positive

I'm not currently working with IBM products because my job has changed. I'm now employed by a different company, and I'm now primarily working with WSO2 products.

We mainly use API Management and Identity Server.

The initial setup is medium, not easy, but also not difficult.

It's a complicated product. There are numerous distinct connections.

We have a maximum of ten engineers working on various parts of the solution and looking after deployment and maintenance.

It was not done by me. I lack experience with the current setup.

We use the open-source version of WSO2 API Manager, there is no cost.

I definitely recommend this solution.

Because the complexity of the setup and the documentation could be improved, I would rate WSO2 API Manager an eight out of ten.

I'm pleased with the WSO2 product, but there are some gaps in the documentation. It could be greatly improved in this case so that it is easier to deploy and maintain when there are issues.

WSO2 API Manager is a complete platform for managing APIs.

I think the best part about WSO2 API Manager is that it's highly customizable because it's open-source. The partnership model is quite lucrative for us, it helps us to go and pitch to our customers. You can build a lot of business models yourself that you want to use. You are able to do a lot of the solutions.

The user interface needs to improve, it is a bit outdated.

There is an Affiliate Marketing monetization in Google Apigee that you would like to use in this solution but is not available. We end up having to build an alternative to get the job done. This feature should be added to this solution.

I have been using WSO2 API Manager for approximately four months.

The solution is scalable, my clients have been happy.

Most of my customers are enterprise-sized companies.

The support system is not that great. The number of employees in the organization is perhaps too little that is providing training. This causes some problems.

I am working with Google Apigee and it is quite nice, but it's a bit expensive for the customers. Otherwise, Google Apigee has a lot of different features that the WSO2 API Manager doesn't provide.

The installation is quite easy, the full implementation takes approximately three months.

I think the other competitors that are providing the same solution are quite expensive. WSO2 API Manager is quite cheap.

WSO2 API Manager is very good for small and medium companies, but if you have an enterprise-level company, Google Apigee might be a better choice.

I rate WSO2 API Manager an eight out of ten.

We use the solution mainly to protect the frontend and backend proxy APIs. We also use the solution for federating with the identity server. We publish our backend API into WSO2 API Manager and use the proxy API outside. We use the solution for authorization, authentication, and accounting purposes.

WSO2 API Manager is quite easy. With WSO2 API Manager, we can use different DBs. It is easy to accommodate the solution along with any kind of identity server. WSO2 API Manager has a user-friendly model.

WSO2 API Manager should improve its marketplace subscription model and documentation in order to reach a higher level in the market.

I have been using WSO2 API Manager for the last two to four years.

I rate WSO2 API Manager an eight out of ten for stability.

I rate WSO2 API Manager an eight out of ten for scalability.

The solution's support model is not very clear enough right now.

Neutral

I previously used the Akamai tool.

The solution's initial setup is very easy. I rate WSO2 API Manager an eight out of ten for the ease of its initial setup.

The solution's deployment takes two to three hours. One person is sufficient to deploy WSO2 API Manager.

WSO2 API Manager is a costly solution, and its pricing is not competitive enough compared to other products.

I would recommend WSO2 API Manager to other users.

Overall, I rate WSO2 API Manager an eight out of ten.

Our primary use case is integration of legacy systems and channels, exposing APIs and security. I'm co-founder and CTO of the company. 

The solution is open source and easy to configure. 

I'd like to see some new features and updated functionalities.

I've been using this solution for three years. 

The solution is stable. 

The solution is scalable. 

The technical support is very good. 

The initial setup is straightforward. 

I would recommend this solution, open source is king. I rate this product 10 out of 10.

WSO2 API Manager is used for digitalization and innovation.

WSO2 API Manager could increase their security compliance.

Here in India, the government is coming with a lot of regulations and required security features which the solutions have to upgrade to meet this requirement. Most of the solutions sell API management as a security solution, but they have to improve the security features.

There are a lot of modules and it can be complex.

I have been using WSO2 API Manager for approximately four years.

WSO2 API Manager is a stable solution.

My customers are not large companies, their volume is less. That is the reason why I recommend WSO2 API Manager because they have a full life cycle of products. For example, they have ESB, API management, and other tools. Additionally, they have webMethods and is quite expensive. 

There is a solution called Gravity which is new that is very good, but they have pure API management which vendors are looking for a full-fledged solution. That is their legacy model, they would need an ESB.

The technical support is good but it depends on the partner relationship.

I would rate the support from the WSO2 API Manager a four out of five.

Most of the solutions similar to WSO2 API Manager have small differences, because of how it fits in their environment. The features that WSO2 API Manager has most of the vendors have too.

I rate WSO2 API Manager a seven out of ten.