This presentation explains how to build a federated API management platform with WSO2 API Manager. It discusses about advantages of API Federation and how different business units within an organization can reuse the same API management platform.

1. Federated API Management with WSO2 API
Manager

2. What is Federated API Management?
• Different business units have their own
timelines and requirements
• Allowing different teams to manage their own
APIs is critical
• How to reuse the same platform while having
the separation

3. WSO2 API Manager
• 100% open source API Management platform
• Support full API lifecycle management
• Componentized architecture which can scale
independently
• Supports hybrid, multi-cloud deployments
• Several options for federated API management

4. Federated API Management with
multi-tenancy
• Logical isolation of tenants on top of the same
API Management runtime
• APIs can be developed in total isolation and if
required, can be shared across different tenants
• Same gateway can be shared across multiple
tenants

5. Federated API Management with
multi-tenancy

6. Using WSO2 API Cloud
• Buy different tenants for different teams
• Cost is higher when number of teams increases
• Less control as a whole
• Less management overhead

7. Federated API management with
Gateway environments
• Shared API publisher and API store
• Different API Gateway environments for
different teams
• Isolation of runtime components
• Ability to share same APIs across multiple
environments while having different scalability
aspects

8. Federated API management with
Gateway environments

9. Federated API Management with
Microgateway
• API gateways can be run in full isolation
• Application specific API gateways with labels
• Lightweight runtime for microservices and
container based deployments
• Can run as a sidecar alongside with the
backend services

10. Federated API Management with
Microgateway

11. 11
Hybrid API Management with API Cloud
• API publishing, Store, Analytics and Security
aspects in the API Cloud
• API gateways (micro gateways) are running on
premise within DBs infrastructure
• API runtime data does not go outside of DB
perimeter

12. Hybrid API Management with API
Cloud

13. API Microgateway as a sidecar
• API Microgateway can run along with the
backend service to reduce the extra hop
• Both can run on the same “pod” in kubernetes
• Can scale both backend service and API
gateway together

14. API Microgateway as a side car

15. Running API Manager on multi-cloud
• Different components can run on different
environments
• Product is supported in multiple cloud
environments (Azure, GCP, AWS, Openshift,
etc.)
• Different teams can move ahead with their
preferred cloud service provider

16. Running API Manager on multi-cloud

17. Layered enterprise architecture

18. THANK YOU
wso2.com