Bring the API culture to DevOps teams
summary
Argues that treating services as APIs accelerates DevOps by improving flow, feedback and experimentation, with concrete examples: using HTTP/REST, OAuth2, caching and hypermedia; a one‑line JavaScript gitlab job log command calls GitLab’s API to retrieve CI traces; a Mattermost slash commands demo shows three custom commands and an echo bot that replies asynchronously and works; cites retail case of a 6x revenue lift (Walgreens) as impact; recommends building an API facade to simplify automation and integrate pipelines, monitoring and chat.
AI-written summary · about
chapters (13)
- 0:00API culture in DevOps
- 5:44Defining APIs and DevOps
- 9:16API design principles
- 13:25Remote calls and web APIs
- 22:13Command-line APIs
- 28:57Why DevOps loves APIs
- 31:23Improving DevOps flow
- 33:54Enhancing feedback loops
- 36:40APIs for experimentation
- 37:21Developer view on API design
- 41:42Conclusion: APIs drive efficiency
- 43:31API integration demo
- 46:36Q&A
related talks
29mWhy APIs Call for 2xs the DevOps
20mAutomated Processes for Even Better APIs
55mBuild your APIs and DevOps Hybrid Skills
29mAccelerate API Innovation: Secrets to Staying Ahead
49mBuilding Software Better: API Lifecycle Management for Developers
25mAPIOps: automating API operations for speed and quality at scale
26mThe GitOps Paradox: Why Your Devs Need an API You Don't Want To Build - Simon Koudijs
27mBuilding Great Web APIs