Live data from Hacker News

Why Dropbox decided to build its own infrastructure and network

techcrunch.com

41–50 of 158 posts

Re: Why Dropbox decided to build its own infrastructure and network

#41
post #34

Earlier quoted context omitted.

I'm against Google hosted amp but what's the issue with self hosted? This page is so much nicer than the overly busy normal TC site.

The problem is you making that decision for me.

Wait, but using the non-AMP version is a decision too. Why do you get to make that one instead? Shouldn't the person posting the link get some discretion?

Re: Why Dropbox decided to build its own infrastructure and network

#42
post #3

Earlier quoted context omitted.

and Netflix?

They run BGP and do an enormous amount of IX peering. https://www.peeringdb.com/asn/2906 AWS doesn't even let you do BGP. If you want to use them for a CDN, you're monopolized into their network and their blend of ridiculously overpriced bandwidth. They might be using AWS for the canonical store of data, but the sanity of using "the cloud" goes out the window the second you need to ship a lot of traffic to the public…

Name a CDN (excluding DDoS mitigation) that offers useful BGP service to customers? Even some CDNs are not quite good at running BGP

Re: Why Dropbox decided to build its own infrastructure and network

#44

Earlier quoted context omitted.

They run BGP and do an enormous amount of IX peering. https://www.peeringdb.com/asn/2906 AWS doesn't even let you do BGP. If you want to use them for a CDN, you're monopolized into their network and their blend of ridiculously overpriced bandwidth. They might be using AWS for the canonical store of data, but the sanity of using "the cloud" goes out the window the second you need to ship a lot of traffic to the public…

> heir blend of ridiculously overpriced bandwidth. For someone not at netflix's level, can you recommend somewhere with significantly cheaper bandwidth.

Pretty much anywhere.

Re: Why Dropbox decided to build its own infrastructure and network

#45
post #21

Earlier quoted context omitted.

I am pretty sure if they desire they can convert CapEx into OpEx.

Sure, if they sell the storage system to someone and arrange a leaseback.

and that someone can be their own subsidiary in a jurisdiction with dif. tax treatment

Re: Why Dropbox decided to build its own infrastructure and network

#46
post #34

Earlier quoted context omitted.

The problem is you making that decision for me.

Wait, but using the non-AMP version is a decision too. Why do you get to make that one instead? Shouldn't the person posting the link get some discretion?

Principle of least surprise. techcrunch.com has a default experience, amp is secondary. Since we can't all read each others minds the default behavior should be to use the ...default.

Re: Why Dropbox decided to build its own infrastructure and network

#47
post #26
post #22

Earlier quoted context omitted.

I am the CEO of a 3 person startup, and this piece has made me realize how critical it is to own your infrastructure if you truly want to disrupt and dominate the industry. I am making our engineers build our own data center at once, and am now hiring for Lead Data Center Engineers (15+ years AWS experience required). :)

They disrupted and dominated their industry while on AWS, and I'm sure it would have been cost prohibitive to do it while young and without customers.

Pretty sure that was a joke.

Re: Why Dropbox decided to build its own infrastructure and network

#48
post #45

Earlier quoted context omitted.

Sure, if they sell the storage system to someone and arrange a leaseback.

and that someone can be their own subsidiary in a jurisdiction with dif. tax treatment

Can be within the same taxing authority. I've facilitated facility transfers and leaseback agreements in the US.

Edit: Yes, you can't seize what isn't owned.

Re: Why Dropbox decided to build its own infrastructure and network

#49
post #25

Can we remove /amp/ from the end of the URL? Some people still use HN on a laptop or a desktop. Also, as mentioned elsewhere in the comments here, it should be retitled to "Why Dropbox decided to drop AWS"

What exactly is /amp/?

Re: Why Dropbox decided to build its own infrastructure and network

#50

Earlier quoted context omitted.

They run BGP and do an enormous amount of IX peering. https://www.peeringdb.com/asn/2906 AWS doesn't even let you do BGP. If you want to use them for a CDN, you're monopolized into their network and their blend of ridiculously overpriced bandwidth. They might be using AWS for the canonical store of data, but the sanity of using "the cloud" goes out the window the second you need to ship a lot of traffic to the public…

> heir blend of ridiculously overpriced bandwidth. For someone not at netflix's level, can you recommend somewhere with significantly cheaper bandwidth.

Pretty much anyone... Hetzner, Linode, Choopa
Post reply on HN