Thoughts about introducing internal developer platforms? The goal of DevOps at the end of the day is to not be a bottle neck and to create pace. The way you create pace is by automating everything so that developers can move at their own pace. Wouldn't introducing IDPs be a good way to do this? In an ideal world, DevOps engineers can template out infrastructure modules for common use cases (think containers, static sites, etc.) Developers then can just deploy the needed infrastructure that will setup and run their applications without needing to be exposed to all the intricacies of infrastructure. If this is true, wouldn't IDPs be the best abstraction layer for developers so that they're not forced to be come infrastructure experts? Has anyone here implemented / built out an IDP for your company? If so, how successful has it been?
Sort by:
CSO in Software3 years ago
Have you heard of Platform.sh? This is exactly what they provide.
Creator Of The Superyacht CRM in Software5 years ago
Ever heard of Go Highlevel CRM? Really good platform that allows for automated marketing strategies in a pipeline structure!
Director of Information Security in Energy and Utilities5 years ago
that's pretty much this way already with fully developed CI/CD processes and YAML templates.
I implemented an opensource IDP (Backstage.io) recently. It was created by Spotify and now is incubated by CNCF with a growth community and several adopters. There are some PaaS solutions, if you don’t want to build an IDP on your own (look here: https://internaldeveloperplatform.org/paas-devops-platforms/).
My advice: bring developer teams to the table. An IDP it's not just an Ops initiative. The IDP adoption journey will be easy if you embrace other teams just in the beggining.