This largely matches my experience working with a team internally who were trying to get Backstage deployed. Or maybe I should say they got it deployed, the lead dev in charge left, and now it sits there mostly used by interns and completely un-serious people who’ve still got the idea that someday it’ll turn into this amazing must have tool that everybody will suddenly adopt.
One of the biggest problems is that they didn’t try to actually interface with other teams to sell why Backstage might be something they want to use. Instead they got it 20% populated with low hanging fruit, and the rest of the company is blissfully unaware that it even exists.
fragmede•6mo ago
The article has ownership information in Backstage is getting out of date and I'm wondering about how that happens for them. Obviously that'll happen if the system doesn't talk to other systems, but (for better or worse) my company's systems connect to LDAP/Entra and access gets granted via group membership. Thus the foo service's admins are in the foo-service-admin group in order for them to have whatever non-backstage admin access their role requires. If the foo service is in the middle of an incident, at the worst you'd start paging the people in that group, no?
pirates•6mo ago
One of the biggest problems is that they didn’t try to actually interface with other teams to sell why Backstage might be something they want to use. Instead they got it 20% populated with low hanging fruit, and the rest of the company is blissfully unaware that it even exists.