Platform Engineering XXL
summary
A corporate internal developer platform called hyperspace IDP is built over three years to serve ~36,000 R&D engineers with a ~350–400 person team and already runs 14,000 CI/CD pipelines; it bundles tools, processes and product management into paved roads (value streams) that encode compliance steps like export classifications, license checks and vulnerability handling. Efforts to untangle decades of siloed tools via expert workshops fail, so the platform composes reusable development procedures, isn’t finished, and is measured by adoption and reduced cognitive load rather than full coverage.
AI-written summary · about
chapters (10)
- 0:00Introduction by host
- 0:43Speaker introduction
- 1:04SAP’s scale and complexity
- 3:55Platform engineering challenges
- 8:49Introducing Hyperspace
- 10:11Paved roads and golden paths
- 14:29Key learnings from Hyperspace
- 16:16Building trust in the platform
- 17:42Selling the vision internally
- 18:48Measuring platform success
related talks
11mBuilding Scalable Developer Platforms
29mIaC Next Steps in Platform Engineering
44mPlatform Engineering 101: Building Internal Developer Platforms
31mPlatform Engineering's Inferno
25mPlatform Engineering: Evolution or a Fancy Rename?
15mEngineering Culture First: The Journey to Building Sphera, monday.com's IDP
44mBeyond Metrics: Orchestrating Developer Delight with AI driven Platform Engineering
29mPlatform engineering maturity - Your key to competitive differentiation