4 ms·
Easily move? It seems to me that you have no serious experience in the real world. There's something called "data gravity", and the non-secondary issue of how t
by simonebrunozzi 10y ago
Easily move? It seems to me that you have no serious experience in the real world. There's something called "data gravity", and the non-secondary issue of how to migrate a "live" system (in production) from one cloud to another over the course of typically several weeks.
Moving from one cloud to another, even with containers, is never easy at large scale.
(source: I have worked at AWS for 6 years, at VMware for 2, and I've seen hundreds of clients go through this exercise)
- jsmthrowaway 10y agoI consider 'toomuchtodo a voice of authority on operations based on much reading and discussion (particularly on moving to physical, which we've discussed before), have performed the very exercise being discussed four times in my own career ranging from a couple cabinets to a couple hundred million in capital, completely agree with the entire comment to which you are replying, and feel that your jab about "serious experience in the real world" was totally unnecessary. If moving operations around is insurmountably difficult, you built operations incorrectly. Put another, even broader, way with a few more implications: if you are totally reliant on one vendor for continuity of any part of your operations, you built operations incorrectly and are introducing unnecessary risk. If us-east-1 goes down and you cease generating revenue as a result, you have built operations incorrectly. That's really all there is to it. And yes, I realize this means 80%, maybe more, of the operations in in the world is built incorrectly. We just learned Snap's is[0]. Maybe even yours! And that's fine as long as you're working on it. Good news: said exercise is a good chance to fix it! Now that half the crowd is inhaling to bombastically retort that undoubtedly controversial, yet completely true, paragraph, allow me to quickly redirect: What's "the real world," anyway? Most of HN forgets a Windows/.NET ecosystem exists, not to mention extra-valley gigs in, say, Nebraska. Would you say the lone sysadmin holding together a hospital in Des Moines is gaining "real world" experience and able to meet you in discussion? Seriously, I hate "the real world" and the people who fire it as a volley during an argument. Even your career is not indicative of "the real world." (Nor is mine.) [0]: Flagrantly so. I've spent the better part of an hour trying to concoct a scenario where that deal is even remotely in the win column for Snap. Still trying. You enshrined a business disincentive (nay, prohibition!) toward optimizing your opex into a five year contract and $400mm a year operating Snap was some kind of win? ... How on Earth? Even with a quarter billion DAUs...
- toomuchtodo 10y agoI really appreciate the kind words, and wish I had more than one upvote for your comment. I'm not here for profit or ego, just to share what I have learned and experienced for the benefit of others. "I am old, here are my mistakes, do not make them" sort of thing. Whether anyone believes it, there's a serious Bay Area echo chamber (which HN overlaps with); there is a whole tech world out there that isn't startup culture/tools/methodologies. If you're ever in Tampa or Chicago, let's grab a beer or dinner my treat. Would love to share war stories.
- eitally 10y agoWhile I agree with your position in principle, I also come from a "legacy IT" world, the kind where systems are moved to public cloud because developers are several steps ahead of the DC admins, or because the CIO wants all net new dev to be on infrastructure he or she doesn't own. These are not "digital natives" (who have no excuse, imho). These are the thick, long tail or large businesses with aging infrastructure and a lack of willingness -- or ability -- to pay for top talent. An additional point is that even the second tier PaaS/IaaS providers (like GE/Predix, for example) are trying to get out of the DC ownership business. There's no compelling reason for them to keep their own DCs when a) it's expensive to run & keep fresh, b) it's CapEx, and c) it costs them expensive heads to organize and manage everything.
- late2part 10y agoSnap shouldn't fit the model of legacy IT. To some degree, myspace did and that's part of why they failed.
- res0nat0r 10y agoI also hate when people say "you should just be able to flip a button and switch cloud providers or regions or you're doing it wrong." That shows about as much of a lack of real world experience as you are bemoaning. It doesn't work that way in real life.
- 10y ago
- throwaway2048 10y ago"never easy" means something entirely different when you are spending billions of dollars on something.
- alexnewman 10y agoActually it is. I just moved about 35k instances and 6PB in s3, multiple many TB pg instamces from AWS to google. It is not that bad anymore. Containers and fast internet make it easyish
- simonebrunozzi 10y agoAlex, I'm curious to hear more about this experience. Did you use any physical device (Snowball, etc), or simply a very fast internet connection between the two? What made you move to Google?
- alexnewman 10y agoActually it is. I just moved about 35k instances and 6PB in s3, multiple many TB pg instamces from AWS to google. It is not that bad anymore. Containers and fast internet make it easyish
- alexnewman 10y agoActually it is. I just moved about 35k instances and 6PB in s3, multiple many TB pg instamces from AWS to google. It is not that bad anymore. Containers and fast internet make it easyish
- alexnewman 10y agoAlso if I could down vote you for saying that person has no experience I would. You just have the data to say that other than not picking the details