Earlier quoted context omitted.
Paying $2500/mo for rent alone on a $50k salary is crazy.
That's why no one does it. They have roommates
and/or they live in the East Bay, where rent is still much more affordable.
Spotify moves its back end to Google Cloud
201–210 of 397 posts
Re: Spotify moves its back end to Google Cloud
#202Re: Spotify moves its back end to Google Cloud
#203Earlier quoted context omitted.
Promises to do something for a year which you can change or withdraw after 30 days are really promises for 30 days: "Google may make changes to this Agreement, including pricing (and any linked documents) from time to time. Unless otherwise noted by Google, material changes to the Agreement will become effective 30 days after they are posted, except if the changes apply to new functionality in which case they will be…
> Disclaimer: IAMALBIANYL. I like that one. :) I have a question though, is the prevalence of taglines in any way related to legal requirements? Do you have to stipulate that you aren't a lawyer when stating things because otherwise people to construe it as legal advice, or is it just a fun little identifier of how valid we should consider information to be (like it is in other acronyms of the same type)?
I think it may stem from laws and rules related to practicing law, but there is certainly not any "requirement" to stipulate you are not a lawyer when speaking about legal things. However there are a few things to be mindful of: In the (all of the) United States (and many other countries) the profession of lawyer or attorney is regulated and requires a license to practice as such. In many places to practice law without a license is a criminal offense. Obviously this doesn't contemplate criminal charges against a group of people spouting off about something legal related on the Internet (otherwise we would have to jail perhaps 80% of reddit), but providing legal advice and interpreting the legal effect of contracts, statutes, or regulations is part of the practice of law.
The reason we heavily regulate the practice of law is similar to the reason we heavily regulate the practice of medicine. If you screw something up, the consequences can be bad. If someone takes your advice thinking you know what you are doing, and you are wrong, that person can end up a lot poorer or even in prison. (Though some will argue we regulate it so lawyers can be the only ones charging high fees for legal advice!) Just like one probably shouldn't go around telling folks not to worry about their incredible chest pain and shooting arm pain unless they are a trained medical doctor, the same could be said for those that go around offering home spun legal advice.. ("Yeah man, if you ask the undercover cop if he is law enforcement, he HAS to tell you! Otherwise it is entrapment man...")
Also the reason you always see lawyers preface everything by saying "I'm not your lawyer.. This isn't legal advice... Yadda yaddda yadda" is because once there is an Attorney-Client relationship a lot of stuff happens. The lawyer has a host of duties to the client, from confidentiality, to competence, and many others. That obligation isn't taken lightly and many times if there is any doubt whatsoever whether or not there is an attorney-client relationship, the law will find in favor of one because --- well -- the lawyer should know better. Therefore lawyers will make it annoying clear they aren't your lawyer before spouting off some deep legal thoughts about whatever the topic of discussion is.
Re: Spotify moves its back end to Google Cloud
#204Earlier quoted context omitted.
So, basically something like AWS's VPC? Given that it took them a few years to get that right even with tons of people asking for it, I'm not super optimistic that Google could match it any time soon. I'd love to be wrong!
GCE networking was always equivalent to AWS VPC, but there's new functionality in stuff like Cloud Router, subnetworks, and other beta features to expand that even more. Here's the Network Services section from a guide explaining GCP for people who are used to AWS: > The differences between AWS networking and Google Cloud networking are significant. This due to the nature of how these services were designed. Google C…
I've always thought that live migration feature is incredible.
Re: Spotify moves its back end to Google Cloud
#205Re: Spotify moves its back end to Google Cloud
#206(Serious question) Isn't it risky to rely on any Google product as a foundation for your business?
They've shut down more popular services that people depend on than Google Cloud. They tend to enter a market, undercut all the competitors, and then once they are dominant in the niche they terminate or change the service in a way that makes it not fulfill the original promise.
Re: Spotify moves its back end to Google Cloud
#207Earlier quoted context omitted.
AWS employees may not speak out very often, but they hardly need to. AWS is a marketing machine, from Jeff's regular blog posts, to the volume of free information they provide and to the conferences that they are running everywhere. I think Microsoft is starting to catch on with Azure promotions & conferences, but it's like Google didn't even know that the there was a race .... and they left their running gear at hom…
This might be true but I think the issue is that many AWS employees actually want to speak out or respond to issues personally. I used to work at AWS and the things we could say were very controlled. It could just be my team/managers though.
No, I agree with your last statement - at AWS you always feel the invisible shadow of PR :)
Re: Spotify moves its back end to Google Cloud
#208Earlier quoted context omitted.
That is true. And, as Spotify found out, what Spotify does can also happen in its own Data Centers :) Google does give an additional level of comfort - seamless scaling, No-Ops, powerful Big Data tools, flexibility. I'm going to shamelessly promote one of my opinions on this topic when it comes to BigQuery: https://cloud.google.com/blog/big-data/2016/02/visualizing-t...
> Google does give an additional level of comfort - seamless scaling, No-Ops, powerful Big Data tools, flexibility. I'm going to bookmark this comment and come back to it when Google decides its getting out of the "cloud" compute business.
Hmm, sounds interesting.
Why do you think they will do so?
Re: Spotify moves its back end to Google Cloud
#209Earlier quoted context omitted.
> Google does give an additional level of comfort - seamless scaling, No-Ops, powerful Big Data tools, flexibility. I'm going to bookmark this comment and come back to it when Google decides its getting out of the "cloud" compute business.
Hmm, sounds interesting. Why do you think they will do so?
Its not their core business. Google constantly exits businesses unless they explode in profitability. As someone who currently uses AWS, it would take an act of god for me to move over to Google Cloud, even if the tools were better and even with the cost of some services (nearline storage) cheaper than AWS.
I'm not just paying for a service. I'm paying because I know AWS is in it for the long haul.
This is great for Spotify, just as AWS was great for Netflix (considering both services are terrible at representing true workloads; they're both just control planes serving static content, videos or music). I don't see it dragging a ton of business into Google, just making their acquisitions easier for people who decide to start on GCP or migrate in.
Just my two cents.
Re: Spotify moves its back end to Google Cloud
#210Sorry 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/ 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…
Spotifier 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.