Platforms, Architecture and Sustainability
summary
Argues that a platform must be a self‑serve API product and splits platforms into developer platform and business capability platform; recommends four pillars: delivery infrastructure, self‑service data, experimentation plus measurement in production, and unified customer touchpoints. Claims carbon is a new resource constraint—data storage and movement matter as much as compute—and reports using simulation and digital twins (plus AI and XR) found a cheaper supply‑chain fix that cut emissions while saving cost. Mentions Green Software Foundation training and cloud‑region shifting as practical levers.
AI-written summary · about
chapters (3)
related talks
34mPlatforms: Defying the laws of IT physics
32mPlatform Engineering for Software Developers and Architects (Redux)
35mSustainable Platform Engineering: Having a Green Thumb Without Shooting Up
28mDriving Sustainability with Platform Engineering
33mWhy You Should Treat Your Platform as a Product
58mPlatforms: Build abstractions, not illusions
12mUnveiling the Future: Navigating Cloud Strategy, Platform Engineering, and Architectural Evolution
51mThe Magic of Platforms