Overview
The article discusses the evolution of Backstage, an open-source framework for building internal developer portals (IDPs) at Spotify, into a commercial enterprise software product. It highlights the benefits of open sourcing the project, the community's contributions, and how this has improved Spotify's internal software practices and developer productivity.
What You'll Learn
1
How to leverage open source contributions to enhance developer tools
2
Why building a community around a software project can improve product quality
3
How to transition an internal tool to an open-source and commercial product
Key Questions Answered
How did Spotify evolve Backstage from an open source project to an enterprise product?
Spotify initially developed Backstage as an internal tool to solve developer experience issues. By open sourcing it, they aimed to establish it as the industry standard for internal developer portals, benefiting from community contributions while improving their own developer practices.
What benefits has Spotify gained from open sourcing Backstage?
Open sourcing Backstage has allowed Spotify to receive valuable contributions from the community, which has led to significant improvements in the platform. This collaboration has enhanced their internal software practices and facilitated the development of a better product for their enterprise customers.
What challenges did Spotify face in balancing internal and external needs for Backstage?
Spotify encountered challenges in meeting the demands of both their internal developers and the external community. They had to ensure that the product remained useful for their own teams while also addressing the broader needs of external users, which sometimes conflicted.
What is the significance of the Spotify Portal for Backstage users?
The Spotify Portal is a SaaS solution that combines the best practices from Spotify's internal development with the open-source community's contributions. It simplifies the process of building and managing plugins, making it easier for companies to adopt Backstage as their IDP.
Key Statistics & Figures
Number of companies using Backstage
3,000
This statistic highlights the widespread adoption of Backstage as an IDP platform.
Number of R&D squads at Spotify using Backstage
700
This shows the internal reliance on Backstage for daily operations and productivity.
Technologies & Tools
Framework
Backstage
Used for building internal developer portals (IDPs).
Saas Solution
Spotify Portal
Offers a commercial product built on the Backstage framework.
Key Actionable Insights
1Consider open sourcing your internal tools to foster community contributions and enhance product quality.By opening up your projects, you can leverage external expertise and feedback, which can lead to innovations and improvements that may not have been possible internally.
2Invest in building a strong community around your software projects.A vibrant community can provide valuable insights and contributions, helping to shape the product in ways that align with real-world needs and use cases.
3Balance internal and external priorities when developing software.It's crucial to ensure that the needs of your internal teams are met while also addressing the broader community's requirements, which can lead to a more robust and versatile product.
Common Pitfalls
1
Failing to balance the needs of internal users with those of the external community can lead to product stagnation.
This often occurs when teams focus solely on external feedback and neglect internal requirements, which can result in a tool that is less effective for its primary users.