How to build a platform that developers love
summary
Starbucks builds a cloud platform in three phases: hand‑built origin, automated evolution, and multi‑tenant expansion; it embeds Datadog in every namespace, provides a CLI and demo environment, and ships a templated GitHub repo with Terraform alerts so a new tenant gets full monitoring in about 40 minutes. Ownership splits platform vs application responsibilities, SREs act as consultant liaisons, and work focuses on automating toil, standardizing dashboards and alerts, and adding cost‑optimization features as a product.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:55Platform Engineering at Starbucks
- 8:15Guiding Principles
- 14:35Getting Started
- 16:19Observability
- 19:16Goal
- 20:41North Star
- 22:16Areas of growth
- 23:51Tooling
- 27:12Whats next
related talks
59mLessons from Running Developer Platforms & Communities
44mPlatform Engineering 101: Building Internal Developer Platforms
40mLessons Learned Building Developer Platforms
27mOvercoming Obstacles and Building Self-service Platforms for Application Teams
43mPlatform Engineering 101: Building Developer Platforms
26mLessons Learned from 7 years of Running Developer Platforms
11mBuilding Scalable Developer Platforms
40mPlatform Wars: The Battle Between Golden Paths and Spaghetti Pipelines