Why everyone speaking "Apish" makes your whole business more agile
summary
Claim: getting everyone to speak APIs turns slow, custom integrations into repeatable, fast workflows. Evidence: a 25-person ERP vendor with 100 customers rebuilds its API using RAML-generated docs and Mulesoft, pilots JSON/REST patterns, runs customer workshops, and ships the improved API in six two-week sprints. Results: customers create Confluence plugins, CRM lead sites and time apps, integrations drop from ~40–60 hours to roughly 20x faster, with automated tests using RestAssured and mock services.
AI-written summary · about
chapters (10)
- 0:00Start
- 4:21TIME FLIES WHEN YOU DEVELOP ARCHITECTURE
- 5:122009 - API 1.0: THE ACCIDENTAL API DEVELOPER REACHES TOOOLER AGE AND LEARNS HOW TO WALK
- 7:482014: NEW IMPROVED PROCESS TOWARDS THE API 2.0
- 10:47WHAT LANGUAGES DO YOU SPEAK?
- 11:19BUT ARE WE REALLY TALKING ABOUT THE SAME THING?
- 16:33EVEN A MONKEY COULD INTEGRATE 2 SYSTEMS GIVEN ENOUGH TIME...
- 19:46GET /CUSTOMERS GET /PARTNERS
- 21:14API CHANGED THE WAY WE WORK
- 21:59LEARNING A NEW WAY OF THINKING...
related talks
54mAPI's a drivers for innovative business models
26mHow to accelerate channel delivery with APIs
21mAPI Evolution: Master the Future of Business Integration
22mAPI and Platform Strategies to Win in Global and Local Markets
25mAPIOps: automating API operations for speed and quality at scale
26mBuilding APIs for Developers & Machines
49mBuilding Software Better: API Lifecycle Management for Developers
25mThe Life Changing Magic of Becoming API First