Building APIs in a Cloud Native era
summary
Argues that real cloud-native APIs are a three-layer stack: utility APIs (atomic business logic), integration APIs (low-code connectors to Twilio, Stripe and arbitrary HTTP endpoints) and edge APIs on gateways controlled by a control plane; recommends Kubernetes secrets, automated Postman-style tests, and hybrid deployments; warns service mesh handles transport not application concerns; cites industry shift to ~75% cloud adoption and shows connector-driven integrations reduce boilerplate and credential risk.
AI-written summary · about
chapters (13)
- 0:00Intro
- 3:10What are APIs
- 4:00Simple example
- 5:00Realistic use case
- 6:45Python SDK
- 7:50Twilio API
- 9:10Complications
- 12:20Drawbacks
- 14:50Integration APIs
- 16:00Characteristics of Integration APIs
- 18:30Why Service Measures are not an answer
- 20:10Problems with APIs
- 23:40Edge APIs
related talks
32mThe Past, Present and Future of Cloud Native API Gateways
27mDon’t put all of your APIs in one cloud
36mApisecure, 14 & 15 March 2023 - David Linthicum, Chief Cloud Strategy Officer at Deloitte Consulting
07mLightning Talk: Why APIs Matter in the Multi-Cloud Strategy
25mSimplifying Cloud with APIs: A Game Changer for Businesses
59mCloud Native Culture
46mThe Cloud Native Diabolical Developer
06mCloud-Native Application Testing Approaches
