Live data from Hacker News

Spotify getting into enterprise IT tools

techcrunch.com

11–20 of 72 posts

Re: Spotify getting into enterprise IT tools

#12

Has anyone successfully implemented Backstage at their company? How'd it go? We're looking at it for an internal platform serving ~50 engineers today, spanning mobile, backend, enterprise integrations, and ML teams. The hope is it'll make it easier to spin up new things "the right way" without e.g. ML PhDs having to learn Helm and K8s, plus other goodies like nice docs.

We use it, and apparently it’s great. It didn’t help with the silos though because I don’t have access.

Re: Spotify getting into enterprise IT tools

#16
post #8

It is tough to keep two widely different businesses under one roof. One is a mature, public B2C, and the other is a dev tooling startup. Spotify should spin off Backstage as a separate company, providing the initial IP and funding and being the first client. Many companies, like Uber, created a lot of useful infra, though they failed to monetize it. They could take a cut in the Chronosphere (M3) and Temporal (Cadence…

> One is a mature, public B2C, and the other is a dev tooling startup.

Amazon/AWS?

Re: Spotify getting into enterprise IT tools

#17
post #7
post #3

I’m not sure who the customer is for Backstage. For a small startup, poking around in the gcp/aws console works well enough. Maintaining another console layer on top of that feels like one more thing that could break. If you’re a big company with a team that could support developer platform tools, you probably have some sort of portal system hacked together and you’ll never be able to change because somebody has a cr…

Backstage is great at slowly migrating dysfunctional organizations into slightly less dysfunctional organizations. I deal with 30 years of random tech debt in a company with immense shadow IT (domains randomly registered, vendors randomly hired to do X, often nobody knows things are still needed, our zonefiles are a mess, unclear responsibilities with our team of 4 being the default fallback), and Backstage at least…

But doesn’t that mean you have a long migration period with two systems to maintain and reconcile?

Re: Spotify getting into enterprise IT tools

#18
My employer is considering using backstage for our data infrastructure tooling. This makes me nervous because Spotify seems unable to program a reliable shuffle feature on their player. Maybe it's because they put all the good devs on backstage?

Re: Spotify getting into enterprise IT tools

#19
post #18

My employer is considering using backstage for our data infrastructure tooling. This makes me nervous because Spotify seems unable to program a reliable shuffle feature on their player. Maybe it's because they put all the good devs on backstage?

Spotify's shuffle algorithm can't be changed easily because too many people rely on its existing quirks. Which means that Spotify's ability to keep it at a reliably stable level of unreliability for so long, through so many other platform changes, makes it a prime example of why Spotify is a perfect choice for enterprise! ;)
Post reply on HN