How to Create a Platform People Want to Use, Not Have To
summary
Taboola’s platform team flips control: R&D can opt out or opt in, and the platform prioritizes projects with real product customers rather than internal tech curiosity. The group builds services jointly with product teams, measures success by company impact not uptime vanity metrics, and hires engineers who understand product pain, not just JVM tuning. Operating constraints include handling ~1M requests/sec and ingesting ~200 TB/day, and the result is a widely adopted, customer-driven platform.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 3:10Growth and infrastructure
- 6:16Freedom and customers
- 8:23Understanding the product
- 10:52Summary
related talks
50mWhy is it so Hard to Create a Great Platform-as-a-product?
26mTwo sides of the platform coin with operator's and customer's voices
39mPlatform Engineering as a (Community) Service
41mPlatform as a Product
28mWhat to Expect from Your Application Platform
33mPlatform as a Product - Transforming from Service Delivery into Continuous Operations
40mInternal platforms in practice
26mThe common fallacies on platform building