WSO2 API Manager Reviews

I recently had the pleasure of using WSO2 API Manager (WSO2 APIM), and I must say it exceeded my expectations in every way. The platform offers a robust and comprehensive solution for managing APIs, making the entire process seamless and efficient.

The user interface of WSO2 APIM could be more streamlined and intuitive.

Official documentation of WSO2 is not easy to understand/comprehensive.

Easily customizable.

Great Support from WSO2 Support team.

Changing scripting languages for the APIM portals when migrating the version might lead to rework of the customized apps.

All problems with respect to managing APIs - authentication, autherisation, logging, security etc

I appreciate the API subscription management feature, which allows for the organized presentation of APIs on the developer portal. It offers robust control over how third parties can consume APIs in a highly adaptable and dynamic manner.

Honestly, I'm not inclined to say that this aspect of the WSO2 API Manager is dispensable. Each feature has its own utility in various scenarios. However, I do suggest integrating the analytics component within the API manager itself, rather than maintaining a separate ELK stack. Configuring ELK independently can be quite time-consuming.

Security: WSO2 API Manager offers robust security mechanisms, including OAuth, JWT, and API key support. It enables fine-grained access control, allowing us to protect our APIs and data from unauthorized access and potential security threats.

Mediation Policies: The platform simplifies the creation and management of mediation policies, enabling us to customize API behavior and data transformations easily. This flexibility ensures that our APIs can adapt to various client needs seamlessly.

Subscription Management: WSO2 API Manager streamlines the process of API subscription, making it easy for developers and clients to discover and subscribe to APIs. This simplifies the API consumption experience and encourages collaboration with external partners and developers.

API Throttling: The built-in API throttling capabilities help us manage and control API traffic effectively. We can set rate limits and quotas to ensure fair usage and prevent overloading our backend systems, ensuring a smooth and reliable API experience for our users.

API Proxy: WSO2 API Manager offers API proxy functionality, allowing us to create a facade for our APIs. This is invaluable for abstracting the underlying complexity, versioning, and routing requests to the appropriate backend services. It simplifies API version management and maintenance.

Lo mas util de api manager para mi es la capacidad de gestionar apis de manara cetralizada, teniendo como ventajas la estabilidad, seguridad, analitica, etc.

Bueno una de las desventajas que veo es la curva de aprendizaje, requisitos de ingraestructura, y la poca documentacion externa, ya que pocos la conocen.

Los problemas que resuelva es relacionados con la gestion de APIs y me veneficio monetariomante

I have tried many API Management solutions as (MuleSoft ,Apigee and SoftwareAg ) WSO2 was the best among them, as it is characterized by a clear and large documentation, as well as the people you will find when inquiring on StackOverflow Collection .

As he is the only open source API Management , one of its advantages is that even if the functionality is not implemented and released, it allows you to develop it and use it by implemeneted a new interfaces.

Until now WSO2 APIM doesn't suppot RAML specification .

Artificial Intelligence capabilities implemented until now, need to be more improved.

The documentation need to be implemented with real samples .

WSO2 APIM won me a lot of time instead of going back to the Backend Team to change or update the API, I do this modification only at the API Manager level, so I don't need a software developer to update and repeat the tests on the Backend again.

The APIs portal is how it is today. The way they display the APIS, the subscriptions and how clients can access, and we as administrators, can also control which API the user will be able to use or not

Some customizations are challenging, and the documentation does not have enough information to help in the task, so some specific development can be difficult but not impossible.

The WSO2 API Manager is solving the API management in the gateway layer. In the same portal, you can access a diversity of APIs, control throttling, provide security etc. The developers don't need to develop those things anymore in their application, making their job easier and worrying only about the business core of the application.

the architecture integrated with the ESB. I like how things work, the separation of the gateway, control and micro/enterprise integrator layer. The XML code is very well separated from the control interfaces and makes maintenance very easy.

A big minus point is the ESB coding IDE, "Integration Studio". There are some very annoying bugs that force us to live with them.

The IDE seems abandoned, the "design" system is more of a hindrance than a help, as anyone who is familiar with WSO2 uses editing via XML. They could remove this functionality, or give the option to disable it, as it makes the program much slower.

basicamente todas as integrações da empresa

Develop a portal for distributing newly published APIs and their documentation

Same as the Identity server, It also looks old. Try to update some new UI/UX and Features

Give access to parallel share with our team members, SO we don't need to give atha API details one by one.

The possibility of performing customizations in the product and the easy install

Some constant bugs happens due to the fact of a lot of updates

He solves the management of APIs in a centralized way and also allows more visibility about the performance of APIs

I like the malleability of the tool in terms of building apis while maintaining security, along with the possibility of customizing the response and I managed to make a soap api available but in a rest full format

I don't like the documentation, but some settings of the tool don't work correctly, like disable cors, we usually have to figure out how it works or even change the tool's deployment settings to make it work correctly.

As a consultant I solve a lot of problems to centralize the API and adjust its response