OpenAPI, an eBay Perspective on the Future API Stack
summary
eBay replaces three legacy SOAP monoliths with a modern REST microservice portfolio built around OpenAPI v3, publishing a full suite of specs so clients generate SDKs automatically. The rollout grows to 23 API families and 250+ endpoints, handles ~1.2 billion listings via a public feed platform, processes >150 TB/day on a 4,000-node Hadoop cluster, serves ~30 billion calls/month (250M peak/hour) and drives ~$19B GMV annually with $150M in API-driven purchases in one quarter.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:47About eBay
- 2:21New Listings
- 2:53International Sales
- 3:19Purpose
- 3:54API History
- 5:08Why do we have APIs
- 6:10What could we do
- 6:39OpenAPI
- 9:14New APIs
- 10:08Global APIs
- 12:21Search API
- 13:36Feed Platform
- 16:00Impact of Feed Platform
- 17:06Impact of eBay API
- 18:14What does that give us
- 20:11APIs are for people
- 21:27How I feel when something just works
- 22:08API Strap Vancouver
related talks
27mKnow Your Developer: Changing Business for the Better
28mThe New API Stack
45mAgile API Development, Bringing Testing and Development Together
15mEvolution of API Management and Emerging Trends
25mAPI, the next 10 years: Beyond the Interface
25mAPIs for the B2B Social Tech Revolution
29m10 years of OpenAPI in the Car Industry
31mOpenAPIs are everywhere