API archaeology: guiding the API journey
summary
Argues that many integrations already behave like APIs and recommends converting high-value exchanges incrementally: identify existing file transfer, data integration (ETL) and application integration (ESB) patterns, pick a small coalition of willing teams, design for change, and publish capabilities so they’re reusable. Claims file-based exchanges remain common and “will stay for at least another decade,” highlights three API goals — unlock resources, deliver experiences as APIs, enable co-creation — and warns scaling the practice, not the tech, is the hard part.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:30Welcome
- 1:58About Axway
- 3:47API archaeology
- 6:57File transfer
- 9:00Data integration
- 10:27Traditional application integration
- 11:27Lessons
- 13:44Advice
- 16:25Design for change
- 17:13Cultivate the landscape
- 17:58Where API can play an important role
- 20:21A word of caution
- 21:10Conclusion
related talks
24mThe Future of API Integration
26mMastering API Strategies for Digital Transformation
21mPragmatic Strategies for Global API Integration
26mAPIs are the new skin of your organisation
27mAPI Economy and Ecosystem
25mAPIs How did we get here and where are we going next
40mThe API mindset: tech, product, business and legal
21mAPI Evolution: Master the Future of Business Integration