Building API Infrastructure in a Decentralized World
summary
Predicts 500 billion devices online, argues API infrastructure must become a decentralized “information broker” and nervous system, and says API management is dead as legacy, monolithic platforms fail in a Kubernetes era. Names gRPC, Kafka, TCP, Kubernetes and tracing as central tools, cites thousands of internal APIs, and predicts gateways will merge load‑balancer features. Pushes an open source‑first stack for visibility, security, routing and operational efficiency.
AI-written summary · about
chapters (11)
- 0:00Welcome to decentralized APIs
- 1:05Connected devices and data in motion
- 4:37Cloud-native and decentralized architectures
- 7:56Legacy systems and thousands of APIs
- 11:06Traditional API management evolving
- 13:53Neural network-like enterprise infrastructure
- 17:22Enterprise API evolution journey
- 20:12Open source for modern API infrastructure
- 23:27Open source in cloud-native tech
- 25:56Open source future of API infrastructure
- 26:42Closing remarks and API Days SF
related talks
01mInterview with – Andreas Krohn
25mRunning a Successful API Program: Best Practices and Challenges
27mLatest Trends in API Management in 2019
48mThe Death of API Management. Welcome to the Funeral
28mThe New API Stack
22mIs the Future of API Management Decentralized?
25mAPI Management - THE key differentiator in digital markets
27mEnterprise API management in agile integration