Building Extensible Platforms - Hazel Weakly
summary
Argues that extensible platforms succeed by choosing a few narrow protocols (think DNS, TCP, JSON) that evolve slowly, enabling wild diversity above and below a constrained choke point; demonstrates the concept of confluence — multiple paths that produce the same end state — to avoid bike-shedding; reframes an “expression problem” for platforms: require static safety for integrations while letting third parties add apps and runtimes without central rewrites; predicts the first ecosystem to nail this vertical integration and bidirectional extensibility wins.
AI-written summary · about
chapters (9)
- 0:00Extensible platforms intro
- 1:03Why extensibility matters
- 2:27Complexity in platform evolution
- 4:11Platform design madness
- 4:56Confluence as principle
- 7:03Narrow protocols for adaptability
- 13:07Platform expression problem
- 19:10Protocols for extensibility
- 21:18Next-gen platforms
related talks
34mPlatforms: Defying the laws of IT physics
51mThe Magic of Platforms
58mPlatforms: Build abstractions, not illusions
46mPlatforms: Build abstractions, not illusions
46mPlatforms: Build Abstractions, not Illusions
47mPlatform Engineering is Domain-Driven Design
29mPlatforms, Architecture and Sustainability
32mPlatform Engineering for Software Developers and Architects (Redux)