Overview
The article discusses Backstage, an open-source developer portal created by Spotify to unify infrastructure tooling and services. It highlights the challenges of managing complex infrastructure and how Backstage provides a consistent interface for developers to streamline their workflows.
What You'll Learn
1
How to create a new microservice using Backstage
2
Why a unified developer portal can improve team efficiency
3
How to follow a pull request from review to production in Backstage
4
When to utilize centralized technical documentation in your projects
Prerequisites & Requirements
- Understanding of cloud infrastructure and developer tools
- Familiarity with microservices architecture(optional)
Key Questions Answered
What infrastructure problems does Backstage address?
Backstage addresses the complexity and fragmentation of infrastructure tools that engineers face as companies grow. It provides a unified interface for various tools, allowing developers to manage their resources more efficiently without needing extensive knowledge of each individual tool.
How does Backstage improve the developer experience?
Backstage enhances the developer experience by providing a single, consistent UI for all infrastructure tooling and documentation. This allows developers to onboard new tools easily, create resources quickly, and access centralized documentation, streamlining their workflows.
What are some use cases for Backstage at Spotify?
At Spotify, Backstage is used for creating new microservices, tracking pull requests from review to production, centralizing technical documentation, and reviewing mobile feature performance. These use cases demonstrate how Backstage simplifies various development processes.
Why did Spotify make Backstage open source?
Spotify made Backstage open source to address common infrastructure challenges faced by many companies. By collaborating with other organizations, they aim to improve the developer experience across the industry and establish Backstage as a standard UX layer for infrastructure tools.
Technologies & Tools
Some links below are affiliate links. We may earn a commission if you make a purchase.
Developer Portal
Backstage
Used to unify infrastructure tooling and services for developers.
Container Orchestration
Kubernetes
Used for deploying services created through Backstage.
Infrastructure As Code
Terraform
Part of the tooling engineers need to understand for cloud deployment.
Version Control
Github Enterprise
Integrated with Backstage for managing pull requests and CI/CD workflows.
Key Actionable Insights
1Implement Backstage in your organization to unify your infrastructure tools and services.By centralizing your developer tools under a single interface, you can significantly reduce the onboarding time for new engineers and streamline existing workflows.
2Utilize Backstage's plugin architecture to customize your developer portal.With over 100 integrations available, you can tailor Backstage to fit your team's specific needs, enhancing productivity and collaboration.
3Adopt a docs-like-code approach for technical documentation within Backstage.This method allows documentation to evolve alongside code, ensuring that it remains relevant and accessible, which can improve knowledge sharing across teams.
Common Pitfalls
1
Failing to integrate all necessary tools into Backstage can lead to continued fragmentation.
It's essential to ensure that all relevant tools are included in the Backstage portal to maximize its effectiveness and provide a truly unified experience for developers.
Related Concepts
Microservices Architecture
Infrastructure As Code
Continuous Integration And Deployment
Technical Documentation Best Practices