Chapter 1. The Platform Imperative: Why Internal Platforms Are Now Essential
In recent years, the challenges of software delivery have shifted. It is no longer enough to ship code quickly. Teams must also ensure that delivery is secure, compliant, observable, adaptable, and resilient. Traditionally, organizations have scaled their engineering efforts by adding more developers, more services, and more infrastructure. Recently, organizations have embraced AI-assisted development, third-party services, and cloud resources. Regardless of the path chosen, the complexity of delivering and operating software has been increasing rapidly.
As discussed in the namesake book by Camille Fournier and Ian Nowland, the concept of platform engineering has emerged in response to a growing disconnect within software delivery.1 While cloud native technologies have made infrastructure more powerful and flexible, they have also made it harder for developers to deliver software independently. Kubernetes, Terraform, continuous integration/continuous delivery (CI/CD) pipelines, and cloud APIs are powerful tools, but they introduce significant operational overhead. Without the right abstractions, developers are forced to wrestle with YAML, wait on tickets, or take on operational responsibilities they were never trained for.
This is where the platform team (or teams in larger contexts) comes in. Its role is not simply to manage tools but also to build a product, an internal developer platform (IDP), that ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access