This meant they could do something amazing. Luckily, the same team that built System-Z was building the internal microservices framework. This key insight highlighted the vulnerability of some systems, and helped bring in changes around microservice management and organization. One of the key learnings was that many services were owned by individuals rather than by teams.
This re-organization process had a positive effect on the whole organization because ownership became very important. Eventually it grew to include information about its relation to other components, and groups of microservices began to be organized into cohesive systems. There would be a link to the code, the name of a team who owns it, and the name of the product owner. System-Z started as a place where Spotify teams could register microservices and their metadata. New engineers were joining every week, and with them, the number of microservices was increasing.Ĭollectively, Spotify’s engineering team realized that it was becoming more difficult to know what we had running in production, and who was responsible for each component.Įventually, one of the platform teams decided to build a catalog of all microservices and to model systems and components in it. She previously worked on the Backstage Core Team at Spotify and was in the room on the day Backstage was first conceived.īackstage was conceived inside Spotify at a time when the company was experiencing rapid growth. This section was written by Roadie Engineering Manager Martina Iglesias Fernández ( linkedin). It has been adopted by many sizes of company in many industry. These include Netflix, American Airlines, Roku, Expedia Group, GoCardless and Wayfair.
Spotify Backstage has been adopted by more than 85 companies (as of Feb 2022). Backstage is the open-source market leader.
WHAT IS SPOTIFY WRITTEN IN SOFTWARE
These factors have driven the need for a developer portal and software catalog solution. Engineering stacks are becoming more complex, onboarding takes longer and collaboration is more difficult. Trends like microservices, Software-as-a-Service, serverless and no-code have resulted in a more chaotic ecosystem for engineers. The catalog allows users to “look up” internal systems to find information about them. It also includes groups of humans, who can own software in the catalog. In Backstage, this can include services, systems, resources such as S3 buckets, and other concepts. The developer portal is typically organized and centered around a service catalog.Ī service catalog, or software catalog, is a list of all of the internal software available inside a company. On a practical level, Spotify Backstage is a collection of TypeScript libraries which can be combined together to create a developer portal. It can be thought of as a single pane of glass, or a hub for software development. It allows them to understand what other teams are working on and how their environments are running. It does this by giving them a place to look up information about their tooling, services and architecture. It aspires to improve software development effectiveness by helping developers focus on what they do best. It was donated to the CNCF soon after release, and is currently a sandbox project.Ī developer portal is an internal website which helps developers make sense of the internal engineering ecosystem. It was created inside Spotify, and used internally there for a number of years, before being open-sourced in March 2020. Spotify Backstage is an open platform for building developer portals.
0 kommentar(er)
