Creating a Scalable and Decentralized API Management Architecture with WSO2 API Manager
1 like362 views
Centralized API management architecture is a common practice in any API management story. With the rapid growth of businesses, centralized API management has become challenging due to issues such as scalability, resource allocations per API, enforcing different security mechanisms, complex API mediations, API shaping, and grouping APIs. A decentralized API management architecture solves all these concerns by enabling you to build a scalable architecture to handle millions of API requests. This solution is based on cloud native technologies for which we have introduced a Kubernetes API operator in WSO2 API Manager. You can use the Kubernetes API Operator to deploy APIs for individual microservices or compose several microservices into individual APIs. This deck will explore how you can create a scalable, decentralized API management architecture with WSO2 API Manager. By doing so, you can create an end-to-end solution for your entire business functionality — from microservices, to APIs, to end-user applications. Discussion points include: - Moving from centralized to decentralized API management architecture - Key concepts in an decentralized API management architecture - Introduction to the Kubernetes API Operator - How to build a CI/CD flow on decentralized architecture Watch the webinar on-demand here: https://wso2.com/library/webinars/creating-a-scalable-and-decentralized-api-management-architecture-with-wso2-api-manager/
![[CB16] Invoke-Obfuscation: PowerShell obFUsk8tion Techniques & How To (Try To...](https://cdn.slidesharecdn.com/ss_thumbnails/cb16bohannonen-161109042710-thumbnail.jpg?width=560&fit=bounds)
![[Workshop] API Management in Microservices Architecture](https://cdn.slidesharecdn.com/ss_thumbnails/apimanagementinmicroservicesarchitecture-191029110253-thumbnail.jpg?width=560&fit=bounds)
Ad
More Related Content
What's hot (20)
Similar to Creating a Scalable and Decentralized API Management Architecture with WSO2 API Manager (20)
![[apidays LIVE HONK KONG] - OAS to Managed API in Seconds](https://cdn.slidesharecdn.com/ss_thumbnails/tharika-apidayshk-2021-210901061904-thumbnail.jpg?width=560&fit=bounds)
Ad
More from WSO2 (20)
![[Roundtable] Choreo - The AI-Native Internal Developer Platform as a Service](https://cdn.slidesharecdn.com/ss_thumbnails/choreo-deck-250328074645-511dded7-thumbnail.jpg?width=560&fit=bounds)
Ad
Recently uploaded (20)
Creating a Scalable and Decentralized API Management Architecture with WSO2 API Manager
- 1. Creating a Scalable and Decentralized API Management Architecture with WSO2 API Manager Pubudu Gunatilaka Technical Lead, WSO2 Dinusha Dissanayake Senior Software Engineer, WSO2
- 2. Agenda ● Typical API Management Story ● Decentralized API Management Architecture ● Building the Solution ● API Operator for Kubernetes ● Deployment modes for APIs ● Live Demo ● Q n A
- 3. Typical API Management Story “
- 4. TRAFFIC MANAGER API PUBLISHER DEVELOPER PORTAL KEY MANAGER API GATEWAY API PROVIDERS API CONSUMERS API CONSUMERS Publish API Push to Store Publish throttling policies Update gateway Access token generation request Key Validatio n API Invocation SERVICE IMPL Subscribe to API
- 5. API CONSUMERS API GATEWAYAPI GATEWAYAPI GATEWAY LOAD BALANCER
- 6. Modern businesses are consumer driven Photo by Joshua Earle on Unsplash
- 7. Breaking down the Monolith Application
- 8. Breaking down the Monolith Application: Delivering services as APIs
- 9. Microservice Architecture Key Aspects ● Testing, deploying and running individual components separately ● Agility, flexibility and speed to market ● Adopt microservice development for fast innovation ● Agile software development life cycles for smaller teams ● Freedom to use heterogenous technologies, early feedback cycles ● Decentralized governance
- 10. Usage of APIs in API Gateway API GATEWAY Food API Store API SMS API Payment API
- 11. Some key concerns... ● Different resource usages ● Different Security enforcements ● Dynamic routing ● API mediation and transformation ● API Shaping ● Response Caching ● Private vs Public APIs ● API Gateway per department/unit API GATEWAY Food API Store API SMS API Payment API
- 13. Addressing the concerns... Store API API GATEWAY Payment API API GATEWAY Food API SMS API API GATEWAY
- 14. ● Lightweight version of API gateway designed for MSA ● Designed to scale ○ ~1s startup time ○ Self-validating tokens ○ Localized rate limiting ○ Offline analytics ○ Immutable and Stateless ● Support for lifecycle management across environments ● Low Resource Environments ○ 40 MB of distribution size and docker base images. ○ < 250 MB of memory. ○ < 1 core CPU. WSO2 API Microgateway
- 16. Why Decentralized API Management Architecture? ● Modern application development practices mandate a more decentralized approach ● Improve productivity and agility by giving teams more autonomy to self-serve ● Microservice philosophy also favours decentralization in all aspects of software design ● At a high level, it is about giving the business greater agility when bringing new ideas to market
- 18. Solution Stages ● API Design Phase: ○ API Creator ■ WSO2 API Manager, Github ● API Approval Phase: ○ API Product Manager ■ WSO2 API Manager, Github ● API Deployment Phase: ○ Fully automated ■ Jenkins, Kubernetes with API Operator, apictl
- 19. API Design Phase ● API Creator designs the API
- 20. API Design Phase ● Use apictl(Command Line tool) to export the API from the API Publisher. ○ You can also download the Swagger definition from the API Publisher. ● Commit the API artifacts to the personal Github Repo. apictl export-api -n Online-Store -v 1.0.0 -r admin -e development git commit -a -m “Adding OnlineStoreAPI” git push origin store-apis ● Make a pull request for API Product Manager’s approval
- 21. API Design Phase ● Github branch structure Github Branch Name food-apis sms-api location-api API Name(s) food-delivery-api sms-api location-api pizza-api restaurant-api API Microgateway 1 API Microgateway 2 API Microgateway 3
- 22. API Approval Phase ● Review and merge the pull request by the API Product Manager ● Login into the API Publisher and publish the API
- 23. API Operator for Kubernetes ● Makes API a first class citizen in Kubernetes eco system ● Easier to deploy ● Imposese ○ Security ○ Throttling ○ Mediation ○ Monitoring For your microservices ● Build in deployment patterns ● Fully automated experience for cloud native API management ● Single source of truth
- 24. API Operator Overview API CRD API Controller API Operator K8s API Server Docker Registry apictl add api -n products-api --from-file=products_swagger.yaml
- 25. API Deployment Phase ● Github release in the respective branch (eg: food-apis-v1.0.0) ● Jenkins job triggers for the release of food-apis-v1.0.0 ● Using apictl (command line tool), add an API in Kubernetes using the API Operator for Kubernetes ● Deploys an API microgateway in Kubernetes ● Ingress resource will be created
- 26. Ingress Traffic Routing ... spec: rules: - host: mgw.ingress.wso2.com http: paths: - path: /review/v1.0 backend: serviceName: review-api servicePort: 9095 - path: /inventory/v1.0 backend: serviceName: inventory-api servicePort: 9095 ...
- 27. CI/CD Workflow
- 28. Deployment Modes for APIs “
- 29. Deployment modes for APIs... ● Private Jet Mode ❏ Scale separately ❏ Dedicated API microgateway for the API Pod API Microgateway Container /API1 Pod Microservice Container Pod Microservice Container
- 30. Deployment modes for APIs... ● Sidecar Mode ❏ Scale microservice with the API microgateway ❏ Dedicated API microgateway for the API Pod API Microgateway Container /API1 Microservice Container
- 31. Deployment modes for APIs... ● Shared Mode ❏ Multiple APIs deployed in the API microgateway Pod API Microgateway Container /API1 /API2 /API3 Pod Microserv ice Container Pod Microserv ice Container Pod Microserv ice Container
- 32. Demo
- 33. Q & A
- 34. ● Demo Artifacts https://github.com/pubudu538/api-operator-demo ● Download and try out: https://wso2.com/api-management/ ● Slack Channel: https://apim-slack.wso2.com ● GitHub: https://github.com/wso2/product-apim/issues
- 35. Webinars to follow ● Apr 30 gRPC Support With API Microgateway 3.1 ● May 5 Deploying GraphQL Services as Managed APIs ● May 12 Overview of API Microgateway 3.1