Ended up with a European support provider (BT Infonet I think) and support in the US via Cisco directly. Oh well; all this just so that we could have Cisco 3650's in a bunch of places.
-
-
The summer after we built all this, I interviewed at AWS. I interviewed at Amazon in Dublin, and I told every interviewer I only wanted to work on AWS. Turns out AWS was building a CDN, but couldn't tell me, and it'd be a good fit.
Show this thread -
I remember telling one of my interviewers (Doug) that the kind of stuff I was doing now was dumb-ass and that AWS would make it history, and that I wanted to be on the right side of that. He was more modest ... that AWS/Cloud could carve out a niche.
Show this thread -
There's a long way to go still, plenty of workloads yet to move. This thread isn't a victory lap for Cloud/EC2. But good god is it hard to imagine a startup in 2019 repeating what we did in 2007/2008. It would be *insane*.
Show this thread -
The entire capacity we built out, which was certainly 10s of people years of effort; lawyers, admins, sysadmins, developers, flights, drives, etc ... I can spin that up in seconds using EC2. Seconds. In more locations! Cheaper!
Show this thread -
That truck worth of servers that took months of negotiation and logistics? Trucks like that pull up to AWS every day! You can even order a SnowMobile truck of ours to pull up to your own site and then come to us. It's mind-blowing.
Show this thread -
One of my favorite parts of my job is that I go to SFBA every month or two and talk with several startup customers. It's so fun to meet people who don't know any other way; who never had to do it the burdensome way. That is very very satisfying! /End-of-thread or AMA.
Show this thread
End of conversation
New conversation -
-
-
Yeah, going by the talks we had about building cages, airgaps and buying shredders capable of doing HDDs then I'm not surprised fancy new cloud world wasn't acceptable.
-
"It all ends up on BitTorrent anyway" never seemed to be an effective argument.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.