Pragmatic Strategies for Global API Integration
summary
Claims a pragmatic path from thousands of legacy components into a mapped platform by aligning tech to an off‑the‑shelf business process model (examples: APQC), reducing cognitive load from thousands to ~50 processes. Advocates right-sized microservices organized by capability, designing HTTP + async APIs as composable API products that represent user flows (order, delivery, tracking), using documentation‑first contracts, decentralized governance and automation that auto‑maps APIs into a published Everything Everywhere All at Once API website that can be monetized.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:45Everything Everywhere All at Once
- 3:35How to get there
- 4:52Microservices
- 5:38Business Capabilities
- 6:02Too Big
- 6:50Nano Services
- 7:21Microservices and Capabilities
- 10:57Business Process Model
- 11:47Architecture Diagram
- 13:27API Products
- 14:30Customer Order Delivery
- 15:47Documentation Driven Design
- 19:27Beware the Competition
- 20:29Conclusion
related talks
26mRevolutionizing Business with API-First Strategy: Key Insights
26mAPI archaeology: guiding the API journey
22mAPI and Platform Strategies to Win in Global and Local Markets
23mLeverage APIs to Transform Your Business Landscape
25mRunning a Successful API Program: Best Practices and Challenges
27mThe API Design Strategy You Need for Growth
19mSolutions Architect. EMEA
27mBuilding Great Web APIs