What is an Internal Developer Platform (IDP)?
An Internal Developer Platform (IDP) streamlines your internal development process to relieve pressure on Ops. IDPs are helpful in compartmentalizing the complexity involved in DevOps and creating a standardized developer workflow on top of all infrastructure and tools. This allows for developer self-service and it prevents a zoo of unstructured scripts caused by unstructured and free-floating scripts.
The impact of IDPs
Let’s look at what impact an IDP actually has on your internal productivity. We’ve used data from teams that have built an IDP internally (Github (2500 developers), Zalando (1000 developers), Sport1 (20 developers) as well as from teams that have built their IDP with Humanitec's products. The data is evaluated by surveying selected teams prior to the integration as well as 6 months after adopting Humanitec/their IDP.
The numbers may differ in your case, but we found the overall impact to be remarkably consistent. So, teams that deployed 1.5 times a week increased their deployment frequency to 6 times a week (which is a 4x increase). Teams that deployed on average once a month, increased by just over 4x to once a week.
Humanitec has an impact on two different levels:
- Overhead necessary to maintain ops setup and serve developers
- Gain in productivity of the development team
Impact on overhead necessary to maintain ops setup and serve developers
Gain in productivity of the development team
A great effect is slightly more qualitative but equally important: teams using IDPs are entirely self-sustainable and become self-responsible. They run the entire end-to-end process. This “self-reliance” element means nothing is being “thrown over the fence” and the ownership level increases while friction between teams decreases.
There is a long list of things you will be missing out on if you are not using an Internal Developer Platform
- You will likely drown in scripts and subsequently maintenance costs. You might say today you’ll just hire more DevOps but this doesn’t scale.
- No matter how hard you try, you’ll not reach the degree of automation possible because you don’t have the necessary scale.
- You have a key-person dependency. Any maintenance update depends on someone who knows exactly what config to change in what file. This works great the first year. But the average time in a job in our industry is 1.4 years.
- Everytime a dev needs a new environment they have to interrupt a colleague in ops and wait for its creation. In the most extreme example we’ve seen in an automotive company this took 3 months per process.
- If an environment is blocked with testing, it's blocked. If you need to ship something you can’t, and if you have to run a hotfix your team is out of the game entirely.
In conclusion: there are two key ways an IDP will impact your team: you will be able to serve developers better with a fraction of the overhead and the productivity will significantly increase. But what’s probably most important is that Humanitec’s Net Promoter Score (NPS) 6 months after initial introduction is above 95%.
If you are interested in more detailed numbers, reach out to us.