Platform Tips #15: Don't be Fooled By Internal Developer Portals
Internal Developer Portal is not a silver bullet and will not solve all your infrastructure and organizational problems. It's one piece of a broader puzzle.
Hey Folks 👋,
I'm Romaric Philogene, CEO of Qovery, and this is my 15th Platform Tips post.
Internal Developer Portals promise a one-stop shop for self-service in software development environments. Tools like Backstage, Port, and Cortex have gained attention for their ability to centralize access to various services and execute workflows based on user inputs. While these platforms undeniably offer a step forward in providing a self-service experience for developers, it's crucial to recognize their limitations and understand why they are not the silver bullet for the challenges faced by Platform Engineering teams.
The Appeal of Internal Developer Portals
At first glance, Internal Developer Portals seem to offer an elegant solution to a complex problem. They present a unified interface where developers can access catalog services and initiate workflows, ostensibly simplifying the developer experience by aggregating resources and tools in one accessible location. This approach aligns with the growing demand for self-service capabilities, allowing developers to operate more independently and efficiently.
The Underlying Complexity
However, the true challenge lies not in the creation of these portals but in the intricate web of connectors that link the portal to the underlying infrastructure. The complexity of ensuring seamless integration and maintaining these connectors can be daunting. It's here that the distinction between an Internal Developer Portal and an Internal Developer Platform becomes critically important.
Internal Developer Platforms go beyond offering a user-friendly interface; they address the core need for automating and unifying the infrastructure that powers these portals. Without a robust platform underpinning the portal, the promise of a seamless self-service experience falls short. The reality many Platform Engineering teams face is that, after investing in portals, they find them barely usable due to the challenge of integrating their existing infrastructure. What's worse, this misalignment demands additional effort to maintain both the portal and the infrastructure, exacerbating the very problems these tools were meant to solve.
The Role of Internal Developer Platforms
This is where Internal Developer Platforms shine. They are designed to automate and unify disparate pieces of infrastructure, providing the glue that binds the portal to the operational backbone of the development environment.
By focusing on the automation and standardization of infrastructure processes, these platforms address the pain points of uniformizing and maintaining the infrastructure, which are often overlooked by portal solutions alone.
A Synergistic Approach
Acknowledging the limitations of Internal Developer Portals does not diminish their value but rather highlights the necessity of a holistic approach to self-service in software development. The key is not to choose between an Internal Developer Portal and an Internal Developer Platform but to understand how they can complement each other.
A truly effective self-service experience requires the seamless integration of a user-friendly portal with a powerful platform that automates the underlying infrastructure.
Side note: I’m pretty sure in 2 to 5 years, Internal Developer Portals and Platforms will converge in a single solution. But it’s another subject that I will develop in a future article.
The Path Forward
For organizations serious about providing a comprehensive self-service experience, the combination of an Internal Developer Portal and an Internal Developer Platform is imperative. This synergistic approach ensures that developers not only have easy access to the services and tools they need but also operate within a framework where these resources are efficiently managed and maintained.
Considerations for Platform Engineering Teams
Platform Engineering teams at the crossroads of deciding between a portal and a platform should consider the following:
Evaluate the current infrastructure: Understand the extent to which it can be integrated with a potential portal solution.
Assess the maintenance overhead: Consider the resources required to maintain both the portal and the infrastructure.
Prioritize automation: Look for solutions that offer robust automation capabilities to streamline operations.
Seek scalability: Ensure that the chosen solutions can grow with the organization and accommodate evolving needs.
Conclusion
Internal Developer Portals represent a significant advancement in providing self-service capabilities to engineering teams. However, they are just one piece of the puzzle. Without the foundational support of an Internal Developer Platform, the full potential of these portals cannot be realized. As we get into the complexities of software development, it's essential to approach self-service not as a problem to be solved by a single tool but as an ecosystem that requires a harmonized solution. By leveraging both Internal Developer Portals and Platforms, organizations can move closer to achieving a truly autonomous and efficient development environment.
Let's revolutionize Platform Engineering by putting developers first. Subscribe now to join me on this exciting journey!