Viktor Farcic

DevOps Is All About Building Internal Developer Platform (IDP) by Viktor Farcic

DevOps engineers tend to be obsessed with their favorite tools and platforms. That could be Docker, Kubernetes, Terraform, Prometheus, Grafana, Crossplane, or any other among miriad of those labeled as "DevOps".

However, that is often missing the point of what we're trying to accomplish. The goal should be to enable everyone to be in full control of their applications, including dependent services and infrastructure. DevOps is about having self-sufficient teams and the only way to accomplish that is by providing services that everyone can consume. Instead of waiting for requests to create a cluster, perform security scanning, deploy an application, and so on, ops and other specialized teams should be enabling others to do those operations.

That enablement is best accomplished by creating an Internal Developer Platform (IDP).

In this session, we'll explore the architecture and the key ingredients needed for an IDP. We'll also discuss the key benefits of an IDP and we'll see, through a demo, how we could build one.

We'll combine tools like Backstage, Argo CD, Crossplane, and quite a few others into a platform that everyone can use, no matter their experience level.

Talk Questions

  • Question 39
    Hiding complexity from app developers through an IDP may end in another silo, what do you think?
  • Question 38
    What happens when the IDP fails, and the developer can't do things by himself?
  • Question 43
    If IDPs are so great, why do so few major businesses (eg. Fortune 500) not use them?
  • Question 41
    in your opinion, using localstack is a good or a bad way of implemeny an IDP on the "dev/test" environment? do you prefer localstack or a test account on your cloud provider?
  • Question 44
    Hi, what is your opinion if you have practical experience of use something as Backastage or Communitec instead of a self-built solution? We are thinking in building a real product oriented IDP, would you look for help outside your organization or you would build and learn form failure?
  • Question 45
    I've worked for companies who built, for example, k8s abstraction layers so devs could do some operations. What is your opinion on building custom solutions when sometimes open-source solutions (in this case helm for example) could be leveraged
  • Question 46
    If we push devs to use IDPs aren't we robbing them of a necessary learning stage of developing their own
  • Question 50
    Would you agree with having an IDP reduces cognitive load for developers and makes them deliver value faster to the company?
  • Question 40
    Can you share some thoughts about IDPs with first-class shift-right support?
  • Question 42
    If devops is something as a "self service" , why do we have devops people, aren't they developers with a mindset of improving the way about how to work alltogether on the company?
  • Question 49
    IDP as I understand seems to be solving the problem of DevOps being DeV support. How do you enable that culture of DevOps building healthy processes using the toolchain, that everybody would be able to use and not just wait on DevOps to do magic? IMO DevOps should provide the process, and be the human factor that manages and monitors them
  • Question 51
    Where do you draw the line for IDP responsibility? What should the IDP do and not do?
  • Question 52
    Considering a CI/CD pipeline, how do you engage the app devs to interact with the deployment notification, when previously they were used to just wait the for the pipeline to pass?
  • Question 53
    If you don't force your users/devs to use the tools, they go wild, mess up and come to you asking to deal with it. Basically waste your time. How to do solve it?