In the cloud-native environment, hardly any other topic has built up such a myth in recent years as the term platform and the associated role of the platform engineer. As with the introduction of the first usable CI/CD pipelines, this gold rush led to rapid adaptation, often without sense or reason. Now that we have arrived in the valley of knowledge, we can deal extensively with the question: do you need a platform, and if so, how do you design and implement it to ensure that it lasts into the future?

To answer this question, we should first look at what constitutes such a platform. A platform is the combination of different capabilities that are required to master traditional and cloud-native environments so that it supports the end user in the development, delivery, and operation of an application. Platforms can be an enabler to turn non-cloud native infrastructures into valuable resources. However, most computing platforms today provide...

Let’s briefly summarize what we have seen so far. A platform puts a bracket around, and a layer of abstraction on top of, your existing infrastructure and environments. The platform enhances it with further capabilities so that your development teams can utilize it in an automated, self-serving way.

From a technical perspective, this represents the next layer of abstraction. Therefore, it is only right to discuss this new fabric we put on top. Going from the bottom to the top, we see the bare metal, followed by the hypervisor for virtualization; this is topped by cloud providers. Some might include containers, Kubernetes, or serverless components – and now, we will add our platform. These are at least four layers, each promising to make the layer underneath simpler and glued together by a hard-to-be-defined meta-level of scripts, Infrastructure as Code (IaC), cloud libraries, and automation. So, do we really need this yet another...

Throughout the next few years, we will see an evolution of cloud computing. In this context, platforms will play a crucial role. On the one hand, the cloud will be everywhere, becoming an abstraction for infrastructure. It doesn’t matter whether this is in the form of edge computing or very specialized services or offers. On the other hand, as we have learned in the previous section, we have to focus on delivering environments that enable the best experience possible for developers and other roles, so those people can focus on generating value. Bringing these elements together practically is the key enablement for an IT organization to keep up the speed with the market while delivering continuous value to your company.

The pervasive cloud

The pervasive cloud is not a single solution. It clusters a variety of cloud-computing capabilities that are undergoing a transformative shift to drive business and innovation significantly...

Designing a successful platform involves much more than technical prowess; it requires a deep understanding of its users’ diverse needs, fostering and motivating collaboration from an early stage, and creating an open environment that welcomes a platform-centric culture. These sociotechnical aspects of platform engineering are crucial perspectives that emphasize not just the technical components of a platform but also the human elements—how individuals and groups interact with the system and how it influences their work and behaviors. Understanding this often invisible part of creating a platform is essential. It is the glue that defines that technologically robust systems are relevant, as well as defining the deeply integrated daily workflows and behaviors of the users. Respecting this almost meta level means enhancing productivity and driving adoption through high satisfaction. We have to acknowledge that every technical decision...

In this opening chapter, we have explored the role of platforms in modern software development, particularly within cloud-native environments. We’ve established that platforms are not just infrastructure elements but elemental products that require strategic planning and continuous refinement to align with evolving technological and business demands.

You have learned about the platform fundamentals, and you recognize the comprehensive nature of platforms that combine software development, operation, and deployment into a cohesive environment. To build on that, you saw why the platform as a product mindset is a key component. It entails continuous development, user engagement, and responsiveness to feedback, to maintain relevance and value.

Then, we discussed the importance of simplifying the developer’s interactions with the platform, significantly reducing cognitive load and operational complexity. Two short tool examples should cause your curiosity and...

• [1] CNCF Annual Survey 2023: https://www.cncf.io/reports/cncf-annual-survey-2023
• [2] Case studies on IDP success:
  • Spotify: https://engineering.atspotify.com/2024/04/supercharged-developer-portals/
  • Expedia: https://backstage.io/blog/2023/08/17/expedia-proof-of-value-metrics-2/
  • Toyota: https://backstage.spotify.com/discover/blog/adopter-spotlight-toyota/
• [3] Gartner 2023 hype cycle for emerging technologies: https://www.gartner.com/en/articles/what-s-new-in-the-2023-gartner-hype-cycle-for-emerging-technologies
• [4] The 5 Core Components of an Internal Developer Platform (IDP): https://internaldeveloperplatform.org/core-components/