API Management and Transformation using WSO2.
Use Cases and Deployment Scope
Pros
- Authentication based on OAuth 2.0 and HTTP Basic Authentication.
- Rate Limiting applied at different levels like Subscriber, API, Resource and Backend.
- Monitoring by exporting the metrics in Prometheus and traces in Jaeger.
- Mediation to perform transformation, orchestration etc.
Cons
- reduce number of portals for configuration like admin, carbon etc.
- improve certificate handling in case of Kubernetes based deployment.
- provide out of the box dashboards for Grafana and Kibana.
- provide more connectors out of the box.
Return on Investment
- Saved almost 500 man-days effort in publishing the TMForum Compliant APIs via WSO2 API Manager compared to publishing the APIs by modifying the Product itself.
- Saved training cost as the self paced training provided by WSO2 are sufficient.
- Able to deliver the project in 30% less time as compared to normal project delivery timelines.