In large organizations, autonomous teams often create a chaotic mix of technologies for similar products, hindering collaboration and developer mobility.
Without a central view of existing technologies, new teams often copy stacks blindly, chase trends, or create yet another fragmented standard.
A digital service catalog provides a centralized solution that balances governance with team autonomy to optimize for time-to-market at scale.
The catalog provides an inventory of all assets, APIs, and standards, which improves discovery, planning, and keeps information fresh through team ownership.
Spotify's Backstage allows you to model domains, systems, components, and APIs as entities to create a clear map of your software ecosystem and its ownership.
A successful governance model centralizes core elements like domains and golden paths while empowering teams with decentralized ownership of their service documentation.
The digital service catalog acts as a support tool that provides structured, transparent data to complement existing enterprise architecture tools and inform IT strategy.
Successfully implementing a service catalog is less about technical effort and more about fostering a company culture of willingness, transparency, and collaboration.
46:24David Leitner
42:02Simon Lasselsberger
29:26Bastian Heilemann & Bruno Margula
26:08Alexander Lichter
30:23Luc Perard
13:57Anna Schoderer & Maximilian Franzke
26:47Kai Geißelhardt & Volker Zöpfel
21:19Maik Wietheger & Jan-Christoph Schlieker
.gif?w=240&auto=compress,format)
Jobs that call for the skills explored in this talk.
Peter Park System GmbH
München, Germany
M&M Software GmbH
Sankt Georgen im Schwarzwald, Germany
Data Reply GmbH
München, Germany
CONTIAMO GMBH
Berlin, Germany
Peter Park System GmbH
München, Germany
Saby Company Page
Sarajevo, Bosnia and Herzegovina
PRODYNA SE
Hamburg, Germany