The Six Stages of Internal Development Platforms
April 13, 2022Categories:
You either die supporting raw Kubernetes manifests, or live long enough to see yourself build an internal developer platform. ~Anonymous
Table of Contents:
- What the Heck is an Internal Development Platform?
- Why am I hearing about this now?
- Designing the Right IDP
- Evolution of an IDP
- Go Forth and Conquer!
What the Heck is an Internal Development Platform?
An Internal Development Platform (IDP) is the system that your organization uses to facilitate developing, deploying, and operating applications. The IDP defines how application developers create, modify, and test their applications, ideally in a self-service manner.
Instead of just handing application teams an AWS root account and saying “have fun”, IDPs seek to provide abstractions that enable those teams to focus on building products, without needing to become DevOps/cloud experts!
As outlined by internaldeveloperplatform.org, the 5 core components of an Internal development platform are:
- Application Configuration Management: Manage application configuration in a scalable and reliable way
- Infrastructure Orchestration: Integrate with your existing and future infrastructure
- Environment Management: Enable developers to create new environments whenever needed
- Deployment Management: Implement a Continuous Delivery or even Continuous Deployment (CD) approach
- Role-Based Access Control: Manage who can do what in a scalable way
Everywhere I turn these days I see another article/talk about companies building internal development platforms on top of Kubernetes:
- 2022-03: Applying Product Thinking to Slack’s Internal Compute Platform
- 2022-02: DevOps MUST Build Internal Developer Platform (IDP)
- 2022-01: Your Internal Developer Platform s**ks!
- 2020-05: More Power, Less Pain: Building an Internal Platform with CNCF Tools
This concept is not actually new! Kelsey Hightower, Joe Beda (and others) have been telling us that Kubernetes is a platform for building platforms since 2017!
Why am I hearing about this now?
At this point you might ask, what is fueling this renaissance of companies building (and publicly talking about) Internal Developer Platforms? In my opinion, it is driven by the rapid maturation of the cloud-native tools that represent the building blocks for these types of platforms. This makes it feasible for smaller teams to build and support platforms that actually work and add business value.
That being said, the Cambrian explosion of cloud-native tools is both a blessing and a curse. While it is more likely than ever that a tool exists that somewhat addresses your particular need, choosing between them and ensuring interoperability is becoming increasingly difficult! (more on this in a future post… but you can find some raw thoughts here)
Designing the Right IDP
The size and complexity of the appropriate platform to suit your organization depends on three main factors:
- The number and nature of the applications it needs to support
- The size and skill set of the application development team(s)
- The size and skill set of the platform development team
Building an internal development process is generally an iterative process and ideally, you will have some early adopter application developers willing to use it as soon as possible and provide feedback to ensure it is meeting their needs effectively.
Below is a rough spectrum (scale intentionally vague) of the different stages an internal developer platform often exhibits within an organization. This is based on my experience working with teams as they build out these types of application platforms and from discussions with others doing the same.
Evolution of an IDP
Stage 0: External Platform as a Service
For very small teams, you likely should avoid building your own platform entirely, and use a 3rd party Platform as a Service (PaaS) while focusing on product iteration and achieving product market fit. There are many options to choose from here including:
- Cloud Foundry
- [App Engine]
Eventually, though, it is likely that either:
- Your workloads no longer fit the constraints imposed by the PaaS 📦
- The PaaS pricing begins to hurt your wallet a bit too much 💸
at which point you may consider migrating off the PaaS, and in the past few years Kubernetes has become the de facto leader for doing so!
Stage 1: Vanilla Kubernetes
When you first move to Kubernetes and are still figuring out how to migrate things, you probably won’t have built out additional abstractions. You will use the raw Kubernetes resource types directly and interact with the cluster via
kubectl. This stage generally won’t last long before moving on to the next stage.
Stage 2: Templating Tools
Very early on you will come across scenarios where you want to have variants of applications running in different environments. There are a variety of ways to accomplish this, ranging from custom bash scripts using
envsubst to more robust tools such as
helm. Your application developers will still need some familiarity with Kubernetes to be successful at this stage.
Stage 3: Initial Internal Developer Platform
Eventually, as the team and applications grow, creating bespoke definitions for each workload becomes unwieldy. To wrangle this complexity you will likely begin stitching together some collection of tools from the CNCF ecosystem to help.
Much of the work at this stage is selecting the tools that best suit your team’s needs and configuring them to play nicely together. This is also the stage where you start to bake more control/opinions into the platform itself and you shape the application developer experience (for better or for worse).
There are several companies and projects such as backstage, humanitec, and shipa that are attempting to help make rolling an IDP easier. It’s worth evaluating these options to see if they will suit your need and/or for inspiration in designing your own.
Stage 4: Extending Existing Platform Building Blocks
As you iterate on your platform, you will almost certainly start to push the boundaries of what existing tools can support or encounter use cases that aren’t quite supported. In this case, you may start to extend those tools (either via a wrapper or a fork) to meet your own needs.
Stage 5 (Optional): Inventing New Platform Building Blocks
At a certain scale/complexity, there might not be an existing tool/project and your custom scripts and glue code are no longer enough. At that point, you might choose to build a new tool to fill the gap.
Stage 6: Full Internal Platform as a Service
At this point, you have come full circle! While the platform will never be complete, a mature internal developer platform starts to look and feel a lot like the 3rd party PaaS you started with, except it has all the specific features your organization needs.
Go Forth and Conquer!
Building an Internal Developer Platform is a significant undertaking, but if done properly can be a force multiplier for application developers and reduce the operational toil of building and operating applications on Kubernetes.
The sooner you start to think about what your ideal IDP might eventually look like, the easier it will be to make decisions that will help you set a course to reach that desired state.
Good luck! 🍀