The Future of Integration: from API to Event Meshes [...]
summary
Argues that the path to event meshes plus API orchestration starts with an architectural visibility map to inventory integrations and spot technical debt, then closes skill gaps, creates shared governance and a center for enablement, and moves teams from centralized delivery to decentralized ownership. Gives a concrete win: a Salesforce flow that originally required four point‑to‑point interfaces becomes a single case updated event topic consumed by four systems, then a fifth subscriber reuses it a month later.
AI-written summary · about
chapters (8)
- 0:00Integration evolution
- 1:52Point-to-point to event-driven
- 3:58API vs event-driven differences
- 6:24Adopting new integration styles
- 9:32Architectural adoption roadmap
- 15:55Future-proofing with AI
- 17:41Change management closing
- 18:27Q&A on adoption
related talks
35mModern API Strategy: From Gateways to Event Mesh
25mAccelerate Event Enabling the API Economy
24mConnecting the World/Cities with Events Flows and APIs Interactions.
24mThe Future of API Integration
25mHow Integration & Api Creation & Life Cycles Are Critical To Your Data Mesh Strategy
16mAPI Integration with JS: Scalable, and Future-Ready Systems
23mEvent API Products: Maximizing the Value of Your Event-Driven Architecture.
37mBuilding Event-driven Apps at Scale