13-Year Technical Evolution: Transforming a Product into a Platform
summary
Company grows from 2006 product to a platform that powers Facebook ticketing and processes about 265 million tickets across nearly 4 million events in 170 countries; first external interface is a 2008 discovery API that pushes event and ticket changes to partners, originally implemented as a single messy file one-file api_pages with username:password in the URL; surprises include hardware that shows nearby events and third parties turning APIs into businesses; KPIs focus on organizers using three-plus integrations for retention.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 5:00API Architecture
- 6:50Most Surprising API
- 8:37Big Mistakes
- 10:27Ecosystem
- 12:34Partnerships
- 14:27SoundCloud
- 16:16Partner Developer
- 22:04Future of Platforms
- 25:07Platform vs Product
- 26:36How did you start
- 29:12Key KPI
- 30:16The craziest idea
- 31:27Cookiecutter
- 32:27Advice
related talks
26mDelivering connected digital experiences with APIs
36mDoubling Down on DevOps: Global Transformation at Ticketmaster
34mCloud Native Transformation: How Ticketmaster is Changing Culture and Speeding Up
28mDevOps in the Enterprise: A Transformation Journey
21mAPI's - a Part Of the Creative Pallet
26m5 billion API hits that have accelerated customer outcomes
16mKeynote: Partnered Leadership
29mAPIs for Biz Dev 2.0 - Which Business Model?