Panel: The Platform Rock-Paper-Scissors: Build, Adopt, Buy
summary
Practical decision rules and concrete tradeoffs dominate: choose vendors when a product clearly outperforms internal work and you need to move fast, prefer open standards and data portability to avoid lock‑in, adopt OSS with active communities and CNCF backing, and build when long‑term differentiation or control matters. Examples: migrate CI to GitOps with Flux or Argo (one migration paid off), measure impact with DORA metrics plus ticket speed and NPS, and expect ongoing maintenance — Chainalysis runs platform work with seven engineers.
AI-written summary · about
chapters (11)
- 0:00Panel introduction
- 1:05Panelist introductions
- 7:47Build adopt or buy
- 12:45Vendor selection criteria
- 18:25Open source evaluation
- 23:22Platform maintenance
- 28:42Platform evolution planning
- 33:17Measuring platform value
- 36:06Internal platform marketing
- 38:36Platform efficiency
- 40:25Inner source encouragement
related talks
38mPanel discussion - Selecting the right technology for the right challenge
43mThinking Architecturally
36mHow to make technical decisions?
40mPractices from trenches for embracing evolutionary architecture in wild
23mPlatform Engineering for Architects - Crafting Platforms as a Product
25mInternal Platform as a Product
58mTeam Topologies Panel
58mPlatforms: Build abstractions, not illusions