It's very expensive and only makes sense if you really need infrastructure sovereignty. It makes more sense if you're profitable in the tens of millions after raising hundreds of millions.
It also makes sense for governments (including those in the EU) which should think about this and have the compute in house and disconnected from the internet if they are serious about infrastructure sovereignty, rather than depending on US-based providers such as AWS.
From what they've said, it's about "spotting" and "identifying" music and music trends. But it seems like mostly it was just a somewhat nonsense word that was easy to remember and whose domain name was available.
Especially since it's popular as a paid service without ads.
So, while "spotify" meaning to add ads, might be fun theory, it does make a lot of sense from nordics point of view..
> We have 730+ days with 99.993% measured availability and we also escaped AWS region wide downtime that happened a week ago.
This is a very nice brag. Given they are using their ddos protection ingress via CloudFlare there is that dependancy, but in that case I can 100% agree than DNS and ingress can absolutely be a full time job. Running some microservices and a database absolutely is not. If your teams are constantly monitoring and adjusting them such as scaling, then the problem is the design. Not the hosting.
Unless you're a small company serving up billions of heavy requests an hour, I would put money on the bet AWS is overcharging you.
My opinion on this: docker sort of changed the game here. It sort of enabled a lot of people to get a "new and fresh" level of abstraction to not bother about bare metal.
As an example, I work in company where most consultants are doing DevOps and k8 is big part of that.
What made me consider that? I've been told multiple times that "you know your stuff" when I mention some kernel or userland feature that container approach provides.
Also maybe, if this approach could yield stats on if some import was needed or not ?
I remember few buddies using similar pattern in ASM that just added n NOP's into code to allow patching and thus eliminating possible recompilation..
This is strongest in the "Sleepytime" episode which is based on the "Jupiter" movement of Holst's "The Planets" . . . honestly I have to skip this episode when it comes up because it makes me tear up so much, and most parents I know who also watch the show have similar reactions. "Sleepytime" is really art.
I seem to recall thinking Gollum was big, but honestly could be remembering the Shelov scene. It was long time ago.