Platforms: Build Abstractions, not Illusions
summary
Argues that platforms must expose the right abstractions not hide reality: a real test is when users do something the platform owner didn’t anticipate (example: a Singapore CD platform repurposed for frequent data updates). Shows cloud scale vs. domain speed: hyperscalers run billions of Lambda invocations but cannot offer domain rules, so build business-specific services instead. Warns against defaults that create illusions (removing 900 pieces from a 1,000-piece puzzle makes it harder) and urges don't mistake composition for abstraction.
AI-written summary · about
chapters (7)
- 0:00Intro
- 2:03We shifted everything so far left, it piled up
- 4:12Economies of scale & speed
- 14:23Platform # IT service
- 22:52Standing on shoulders of giants
- 27:48Abstractions vs. Composition
- 45:52Outro
related talks
46mPlatforms: Build abstractions, not illusions
58mPlatforms: Build abstractions, not illusions
48mBuild Abstractions Not Illusions
34mPlatforms: Defying the laws of IT physics
51mThe Magic of Platforms
29mPlatforms, Architecture and Sustainability
47mPlatform Engineering is Domain-Driven Design
23mPlatform Engineering for Architects - Crafting Platforms as a Product