How to build better and consistent APIs at scale
summary
Adidas runs a landscape of 400+ APIs and recommends balancing central rules with team autonomy, codifying contracts with tools like Spectral, and automating CI/CD so API contracts and pipelines stay in sync. Use Kubernetes ingress and modern gateways such as Ambassador / NGINX Plus to let product teams publish directly, enforce policies via admission controllers, and adopt a gitops workflow for declarative deployments and PR-driven API publication. Cataloging remains hard; consider runtime registries (curio), Amundsen or Superface for discovery.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:40About Samir Amzani
- 1:23The model of all problems
- 1:49How we build applications faster and cheaper
- 2:38The main concern
- 3:11The basic answer
- 3:31Standardization
- 3:50API Composition
- 4:08Error Management
- 4:38Implementation
- 5:04APIs Tabs
- 5:22Automation
- 5:45Governors
- 6:04EPA Team
- 6:49EPA Lifecycle
- 8:06Example
- 8:53API Exposure
- 9:40API Publishing
- 9:55Kubernetes Integration
- 10:40Gitops Workflow
- 11:03Visibility
- 11:48API Catalog
- 12:15Public APIs
- 12:58Tools
- 13:35Summary
related talks
24mAPI design is where culture and tech meet each other
28mMaximize API Growth: Strategies from Industry Experts
27mEnterprise API management in agile integration
26mBuilding successful API developer programs
25mAPIs for Scaling Enterprises: Setting and Applying API Standards.
25mAPI Digital Transformation in Adidas
38mAPI Mastery: from the Design to Development
24mSelecting the best API Governance for your organization