Platform Engineering is Domain Driven Design
summary
Argues that platform engineering equals Domain-Driven Design: build a domain-specific language that maps to cloud automation, reference architectures and golden paths so developers can self-serve. Shows an in-house CI/CD platform for Singapore that unexpectedly becomes a data-distribution pipeline, a financial client building a ledger database tailored to compliance, and warns against collapsing the top of the double pyramid. Uses AWS primitives (Lambda, SQS, managed DBs), cites ~30 BMW models and billions of deploys/day to justify scale vs speed, and shows the platform worked when teams did unanticipated things.
AI-written summary · about
chapters (8)
- 0:00Introduction to platforms
- 2:25Platforms and cognitive load
- 8:02Economies of scale vs speed
- 15:41Dynamic model for platforms
- 22:01Abstraction and naming in platforms
- 31:35Cognitive load and interfaces
- 37:10Domain-driven platform design
- 45:35Generative AI and platforms
related talks
47mPlatform Engineering is Domain-Driven Design
32mPlatform Engineering for Software Developers and Architects (Redux)
26mThe Past, the Present, and the Future of Platform Engineering
23mPlatform Engineering for Architects - Crafting Platforms as a Product
51mThe Magic of Platforms
29mPlatforms, Architecture and Sustainability
58mPlatforms: Build abstractions, not illusions
24mSignificance of Platforms in Product Development