WSO2 API Manager Reviews

I use the solution in the telecom sector.

The most valuable feature of the solution stems from the fact that it is a free tool. Functionality-wise, I like WSO2 API Manager - Publisher API and WSO2 Enterprise Service Bus.

In the future releases of the product, I hope WSO2 API Manager remains available as an open-source product. In the Gulf region, there is a great need for open-source technologies.

WSO2 API Manager should be always available to users as an open-source product that is license-free. In that case, it will be very much appreciated and used in the Gulf region and Saudi Arabia.

I have been using WSO2 API Manager for two years.

Stability-wise, I rate the solution a seven to eight out of ten.

Scalability-wise, I rate the solution a six out of ten.

Around 15 developers and the end users or consumer users are about 1,000 for the tool.

There are no plans to increase the use of the solution.

I rate the product's initial setup phase a five on a scale of one to ten, where one is a difficult setup phase, and ten is an easy setup phase. Initially, any developers, integration experts, or guides have complete knowledge of how to install the tool. For fresh graduates and engineers, the setup process can be very difficult.

The solution is deployed on an on-premises model.

The solution can be deployed in an hour.

There are no subscriptions or licenses required to operate the product, like in the case of Apigee and IBM API Connect. It is an open-source product.

I recommend the product to small companies, and whichever other companies need to deploy WSO2 API Manage should go ahead and use it since it offers the full set of functionalities offered by similar tools like Apigee vs IBM API Connect.

I rate the overall tool an eight out of ten.

WSO2 is accessible. Even a beginner can have an idea of what's going on.  It has a drag-and-drop graphical interface, so it's a low-code platform that enables you to effortlessly get things done.

The user interface is easy to navigate, and the documentation is extensive. It's open-source, so everything is available, and we can create what we need. That's not necessarily a feature, but it's an advantage. 

They are developing another platform called Choreo that allows you to create API itself using the WSO2 programming language Ballerina. It would be great if they added a direct connection between Choreo and API Manager, that would be great. I think they are working on that, but I'm not sure.

I used API Manager a few months ago. I briefly touched on those areas during my internship, but I haven't gone that deeply into the product. I don't have implementation knowledge, but I have a rough idea about what's going on.

I rate API Manager 10 out of 10 for stability. 

I rate API Manager 10 out of 10 for scalability. It's suitable for small companies or large enterprises. 

I haven't contacted WSO2, but I know that they provide good support. 

The cost is reasonable even for Sri Lankan companies.

I rate WSO2 API Manager 10 out of 10. Don't hesitate to use it. Most people can start with WSO2 API Manager because it's easy to find what you need in the documentation. I recommend newbies start with WSO2 API Manager.

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 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.

WSO2 API Manager serves as a central hub for integrating sensors across SmartCity projects. We provide support for developers, enabling them to build applications using our platform. Our use cases include features like spotlighting, forecasting, and environmental monitoring. We also offer security management through WFO protocols for responsible and secure environment for our users.

WSO2 API Manager is open-source, which offers a range of features not found in other open-source API tools. The user interface is another standout feature that we appreciate. In terms of effective features for API life-cycle management, we use the tool for licensing, allowing us to differentiate rates based on customer numbers and end-user data publishing.

Regarding security features, WSO2 API Manager is a robust compliance solution, especially for AWS usage. It offers deployment management, performance-based security, and overall compliance support.

I would like to see improvements in the speed of the solution as it can be a bit slow compared to other platforms along with addressing memory issues would be beneficial.

I have been using WSO2 API Manager for the past five years.

We experienced some stability issues, particularly related to memory, which affected the database performance.

WSO2 API Manager is scalable and suitable for our project needs. We have around twenty to twenty-five actual users who access the platform for deployment and management purposes.

I have interacted with technical support in the past, and they have assisted us with our queries. They were helpful overall, although some complex issues took longer to resolve.

Positive

I have experience using another API management solution from a larger company. Comparing WSO2 API Manager, it has its strengths in flexibility and customization based on our requests. It also has robust features and components. But in terms of cons, it can be complex and may take some time to set up compared to simpler solutions.

The setup was a bit complex because we initially started with enterprise professional services, but later transitioned to the open-source version which required more effort to set up.

We didn't encounter many challenges while integrating WSO2 API Manager with other systems as we primarily focused on setting up our own solution. We mainly relied on the solution itself for updates and upgrades.

Our deployment involved setting up two rings in the cluster and transitioning from testing to production. It took some time to learn the deployment process, especially with the enterprise version.

We completed the set-up in-house. One person is required for handling the deployment for the enterprise aspect.

We haven't implemented any AI-driven solutions or encountered AI-driven issues within our company.

I would recommend WSO2 API Manager to other users, especially if they value a robust support system and are ready to invest in the deployment process. However it is important to consider factors like support costs and licensing models before making a decision. 

In terms of overall rating, I would give it a seven out of ten, taking into account both its advantages and limitations.

We are using the solution for authentication purposes.

The tool is easy to manage.

The product is easy to use. It is pretty simple to configure the solution. It's pretty easy to set it up and use it.

The technical support must be improved.

I have been using the solution for two to three years.

I rate the tool’s stability an eight out of ten. We didn’t face any issues with the solution.

I rate the tool’s scalability a nine out of ten. Around 50 to 100 people are using the solution in our organization.

The on-site document is okay.

Previously, we used IBM. We switched to WSO2 because it is easy to get and costs less than IBM.

The tool is pretty easy to install. We need 30 minutes to install it.

We need two systems engineers to maintain the tool.

I would recommend the solution to others. Overall, I rate the product a nine 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.