API-Driven Microservice Architecture: Empowering Digital Transformation
summary
Argues that APIs plus an API gateway remove client-to-microservice spaghetti and enable security, throttling and caching centrally, demonstrating WSO2 tooling: WSO2 API Manager and the micro gateway for offline token validation, plus two integration options—code-first with the Ballerina language and a lightweight Micro Integrator—used to build integration microservices. Proposes grouping services into immutable, deployable cell-based architecture units (build cell spec, create cell image, push to cell hub) to manage hundreds or thousands of services.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 0:18Pebbles vs Boulders
- 1:41Agenda
- 2:36Issues with Direct Client to Microservice Communication
- 4:25API Gateway
- 5:00API Gateway Solution
- 5:22WSO2 API Manager
- 9:26WSO2 Solution Mapping
- 9:43Ballerina
- 10:39WSO2 Enterprise
- 12:34Ballerina Integration
- 12:59Micro Gateway
- 14:25Layered Microservice Architecture
- 15:09Microservice Graph
- 16:13Cellbased Microservice Architecture
- 17:13Cellbased Architecture
- 17:58Details about Cellbased Architecture
- 18:46Cellbased Architecture on Kubernetes
- 20:07How it works
- 21:29Define it
- 22:05Summary
- 22:50More information
- 23:21Seize the day
- 23:35Conclusion
- 23:46Questions
related talks
23mLeverage APIs to Transform Your Business Landscape
29mImpact of Microservices Architecture on API Management
27mMaster API Gateways: Boost Your Microservices Strategy
23mDecentralized API Management for Agile Enterprises
26mBuilding Scalable Microservice APIs From The Beginning
39mWelcome To The Era Of Microservices
23mMicroservices Architectures: Agility vs Complexity
06mHow to be API-centric and microservice friendly