Um, what is this crap? When did they actually move? How long did it take? The title of this HN link leads you to believe this is recent, but the article makes it seem like a multi-year effort, that in fact, could have finished a long time ago.
Why Dropbox decided to build its own infrastructure and network
11–20 of 158 posts
Re: Why Dropbox decided to build its own infrastructure and network
#12Um, what is this crap? When did they actually move? How long did it take? The title of this HN link leads you to believe this is recent, but the article makes it seem like a multi-year effort, that in fact, could have finished a long time ago.
Re: Why Dropbox decided to build its own infrastructure and network
#13Re: Why Dropbox decided to build its own infrastructure and network
#14Earlier 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…
Netflix rolls its own CDNs because Cloudfront can't meet all their demands, yet.
Re: Why Dropbox decided to build its own infrastructure and network
#15Um, what is this crap? When did they actually move? How long did it take? The title of this HN link leads you to believe this is recent, but the article makes it seem like a multi-year effort, that in fact, could have finished a long time ago.
I agree. The title is misleading and should be changed.
The timeline is really, really significant here. Did they initiate this back in 2013? 2015?
My company has seen a remarkable shift in trust for online services change the last two years. Was Dropbox ahead of this curve? Were they someone who brought this change in mentality around?
This blog article is crap because without a basic sense of _when_ it could be that they were riding the coattails of other industry leaders. Or they were leading the charge.
Re: Why Dropbox decided to build its own infrastructure and network
#16This means their EBITDA now probably shows profitability (servers they own are amortizable [the A in EBITDA], where are AWS is expensed.) Edit: Amortization/Depreciation can generally be used interchangeably.
Re: Why Dropbox decided to build its own infrastructure and network
#17Um, what is this crap? When did they actually move? How long did it take? The title of this HN link leads you to believe this is recent, but the article makes it seem like a multi-year effort, that in fact, could have finished a long time ago.
Re: Why Dropbox decided to build its own infrastructure and network
#18Re: Why Dropbox decided to build its own infrastructure and network
#19This means their EBITDA now probably shows profitability (servers they own are amortizable [the A in EBITDA], where are AWS is expensed.) Edit: Amortization/Depreciation can generally be used interchangeably.
Maybe but OpEx is tax deductible. CapEx is not.
Re: Why Dropbox decided to build its own infrastructure and network
#20Earlier 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…
For someone not at netflix's level, can you recommend somewhere with significantly cheaper bandwidth.