3 ms·
Sorry but spotify's infrastructure is not a shiny beacon of correctness. They've compounded mistake upon "Oooshiny lets use that" here is a post where someone
by KaiserPro 11y ago
Sorry but spotify's infrastructure is not a shiny beacon of correctness.
They've compounded mistake upon "Oooshiny lets use that"
here is a post where someone dissects spotify's infrastructure bit by bit: http://www.secretbatcave.co.uk/software/docker-and-you/ http://www.secretbatcave.co.uk/software/docker-and-you/
This isn't an anti google compute, its got some really great features. But, spotify's backend infrastructure ain't one
Yes, I appreciate that that post is from a while ago, and they might have completely paid back that massive technical debt/innovation token debt.
- rohansingh 11y agoTo be fair, the presentation that that article is using as a reference for Spotify's infrastructure was from 3 years ago, and during most of the presentation I talked about what was wrong with how we were doing things. How we do things is quite different now. Check out my DockerCon 2014 presentation or our tech blog for details.
- nrh 11y agoSpotifier here. For the record, I hate puppet with the fiery intensity of a thousand suns. It's also pretty hard to magically make go away. I could probably do a whole talk on why puppet is difficult to kill, it's the kudzu of config management. I think it is the worst. We've got our warts and a pile of tech debt, and I wouldn't want anyone to think otherwise. Containers are a part of a long-term strategy to get away from puppet and onto more idempotent units of deployment, and move a lot of what is considered to be "configuration" back into the build process where it belongs.
- laxk 11y agoIs there any public available information where we can read about deployment process in the company?