WSO2 API Management Journey — 2.x to 4.x
In this story I will try to jot down my experience with WSO2 API Management.
When did I started with WSO2 API Management?
It started in January 2019 when we were looking for Open Source API Management platform that can cater to our needs. This includes managing our APIs with fulfiling our cross-cuttting concerns like API Lifecycle management, Security, Third Party Management, Developer Portal and other features that makes the use of API Management tools sensible to use in any sized organization.
WSO2 APIM version journey
Started with WSO2 version 2..2.0 with a small POC to understand if this meet our needs. We used zip archive for deployment, and it was straight-forward for both Windows and Linux ecosystem (although initially they provides lot of other deployment options like windows installer, rpm, deb packages, docker images, helm charts and others).
Once our POC was over and we were starting with the development, WSO2 APIM 2.6.0 version arrived. So, this was the next version with which we have started our original product. Not much changes in terms of UX or features, but as we were using the REST Management APIs so we have to update the version of that (v0.12 to 0.14).
Those interested in previous versions can go to below link which lists all:
A big change was arriving, yes, it was version 3.0.0
With this version, WSO2 APIM Developer community has witnessed the new design of APIM. This was movement from Jaggery Apps to React, form based security to OpenID connect.
Noticeable features for 3.x series
WSO2 has released three versions as part of 3.x series — 3.0.0, 3.1.0, 3.2.0.
- All the configurations moved to “deployment.toml” file instead of requiring the developer to update multiple files like api-manager.xml, carbon.xml.
- Developers can now choose to make MTLS as mandatory and introduction of API Keys.
- Whole new capability of Products, with which organizations can offer related APIs as an offering to third parties.
- Third party OAuth 2.0 and OpenID connect Key Managers like Okta, Keycloak now supported alongwith Resident Key Managers (version 3.2.0)
Issues faced with Version 3 series
Major issue faced with 3.x series was related to publish API using swagger specification. This issue start coming from version 3.0.0 and it was in 3.1.0 and in 3.2.0 as well. Here is the link for the same:
But, WSO2 team is there to answer all out queries
I would like to appreciate WSO2 team for their promptness in serving our problems, participating in discussions via various channels.
WSO2 has dedicated Slack channels for all its product lines — APIM, IS, Enterprise Integrator.
You can join WSO2 APIM Slack channel here.
I would also like to mention about WSO2 Community Calls as open platform where a new topic is taken to discuss with community.
WSO2 APIM 4.x Series
Finally, I would like to close this story mentioning about the WSO2 APIM version 4.x series. Recently, WSO2 has released version 4 which has introduced features like adding integration service powered by their Choreo Plaform, streaming service supports and others.
I am bit disappointed with this release in terms of Analytics. Analytics server is now replaced with Choreo Analytics, which is WSO2’s cloud based Analytics service.
This will affect the organiations using WSO2 in many ways:
- Most of the organizations have customized API analytics as per business needs.
- Since it is cloud based only, organizations are bound to use this (if anyone from WSO2 is reading this story, kindly confirm if on-premise version available)
- As confirmed with them over the Slack Channel, old Analytics data cannot be migrated to Choreo.
Features of Version 4.x series can be find here:
On a positive note, looking forward to manage APIs with WSO2 APIM.
