Platforms: Build Abstractions, not Illusions • Gregor Hohpe • GOTO 2025

2026-06-29 · Source: GOTO Conferences · Field: Technology & Digital — Software Development & Engineering, Cloud Computing & IT Infrastructure · Depth: Advanced, extended

Summary

Gregor Hohpe's GOTO 2025 talk, "Platforms: Build Abstractions, not Illusions," explores the critical distinction between effective platforms and mere IT services or compositions. He argues that modern software development faces increasing cognitive load due to shifted-left responsibilities, which platforms aim to alleviate. Hohpe differentiates platforms driven by "economies of speed" from traditional "economies of scale," advocating for designs that foster diversity and innovation atop a standardized base, rather than a restrictive pyramid model. Citing examples from the automotive industry and cloud providers, he highlights that true platforms enable users to achieve unanticipated outcomes. The talk warns against creating "illusions of simplicity" where abstractions merely hide underlying complexity, emphasizing that good abstractions introduce new, domain-specific vocabulary and remain robust despite implementation changes. Ultimately, successful platforms utilize deep business domain understanding to offer services that hyperscalers cannot.

Key takeaway

For CTOs and platform architects evaluating or building internal platforms, prioritize creating genuine abstractions that reduce cognitive load and enable innovation, rather than merely composing existing services. Focus on delivering domain-specific services that hyperscalers cannot, utilizing your organization's unique business understanding. Ensure your platform fosters diversity and speed through self-service and low-friction guidance, avoiding the illusion of simplicity that ultimately leaks complexity and hinders developer productivity.

Key insights

Effective platforms reduce cognitive load by providing intuitive, domain-specific abstractions that enable unanticipated innovation.

Principles

• Platforms prioritize speed, not just scale.
• Abstractions must not create illusions.

Method

Design platforms to offer domain-specific services that cloud providers cannot, by leveraging deep business understanding. Employ new, intuitive vocabulary for abstractions, and integrate low-friction guidance like automated compliance checks.

In practice

• Use type systems for intuitive design.
• Implement rapid feedback mechanisms.

Topics

• Platform Engineering
• Abstraction Design
• Cognitive Load Reduction
• Domain-Specific Platforms
• Internal Developer Platforms
• Cloud Strategy

Best for: Software Engineer, DevOps Engineer, CTO

Related on AIssential

• State of the Art of Platform Engineering • Abby Bangser & Charles Humble • GOTO 2026 — Platform engineering must provide self-service, API-first, deterministic capabilities to enable scalable, compliant AI agent consumption.
• How Platform Engineering Using Golden Bricks Can Enable Fast and Smooth Delivery — Platform engineering must treat developers as customers, offering composable "golden bricks" to reduce cognitive load and accelerate delivery.
• Data Mesh, Data Platform, or Data Chaos? Choosing the Right Ownership Model (Data #3) — Effective data ownership scales through intentional hybrid structures, not by choosing between centralized or decentralized models.
• Building and Scaling a Platform with Project-as-a-Service — Shifting from full developer autonomy to a "paved road" with Project-as-a-Service reduces cognitive load and increases standardization for platform adoption.
• The Localhost Ego Trip — Over-reliance on self-hosting one LLM can hinder optimal architecture and obscure true engineering challenges.
• Picking an Experimentation Platform: A Retrospective — Platform selection needs rigorous process, but organizational vision and post-contract change management are critical for true experimentation success.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by GOTO Conferences.