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