"We’re talking about a company that had 1500 employees, with just around a dozen on the infrastructure team" - what the rest 99% of the company is doing, marketing?
Why Dropbox decided to build its own infrastructure and network
51–60 of 158 posts
Re: Why Dropbox decided to build its own infrastructure and network
#52Dropbox hasn't dropped AWS, they moved things off AWS as it made sense to. The article is talking about two things, the move of file storage and a network backbone. Neither of which were done recently. The file storage move from S3 to Magic Pocket is detailed in these blog posts: https://blogs.dropbox.com/tech/2016/03/magic-pocket-infrastr... https://blogs.dropbox.com/tech/2016/05/inside-the-magic-pock... https://blo…
From the last link, in 2016 "Proxy-Stack deployed at our edge PoPs to terminate SSL connections closer to our users".
Reminds me of the infamous "SSL added and removed here! :^)".
Does anyone know if there are any additional protections from snooping on their internal network?
edit: phrasing
Re: Why Dropbox decided to build its own infrastructure and network
#53Can 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/?
A path we don't wan't the web to go, forced by Google for their own interest.
Re: Why Dropbox decided to build its own infrastructure and network
#54Lack of IT incompetence is exceedingly rare in the antihardware industry.
Re: Why Dropbox decided to build its own infrastructure and network
#55Earlier quoted context omitted.
> heir blend of ridiculously overpriced bandwidth. For someone not at netflix's level, can you recommend somewhere with significantly cheaper bandwidth.
Any colo or dedicated server provider.
At a CoLo I have the rack, managment, and hardware overhead too, though? Also fewer PoP.
EDIT: I guess I was talking about CloudFront specifically, not EC2. EC2 is pretty pricey.
Re: Why Dropbox decided to build its own infrastructure and network
#56Can 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
#57Earlier quoted context omitted.
> 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
For those I need to run a VPS, which also costs money and has fewer PoP and more mangment overhead.
EDIT: I guess I was talking about CloudFront specifically, not EC2. EC2 is pretty pricey.
Re: Why Dropbox decided to build its own infrastructure and network
#58> While cost is always something that we consider, our
> goal with our network expansion was to improve
> performance, reliability, flexibility and control
> for our users — which we have succeeded in doing,”
> a company spokesperson told TechCrunch.
Who believes this?
It was, easily noticable by everyone, wanting to reduce the cost. Which is fine, everyone does so, so why not admit that it was the primary impetus?
I would not want to outsource control over any larger company that I were to run to other, even bigger companies.
Re: Why Dropbox decided to build its own infrastructure and network
#59"We’re talking about a company that had 1500 employees, with just around a dozen on the infrastructure team" - what the rest 99% of the company is doing, marketing?
I was also thinking that those numbers are really weird, for a company which does infrastructure(fileservers)-in-the-cloud. Obviously some devs doing software for various platforms, business-side folks and so forth. But 1500:12 is a really weird ratio, given the core function of the business. If they're not spending on infra staff... what staff are they spending on?
Re: Why Dropbox decided to build its own infrastructure and network
#60Dropbox hasn't dropped AWS, they moved things off AWS as it made sense to. The article is talking about two things, the move of file storage and a network backbone. Neither of which were done recently. The file storage move from S3 to Magic Pocket is detailed in these blog posts: https://blogs.dropbox.com/tech/2016/03/magic-pocket-infrastr... https://blogs.dropbox.com/tech/2016/05/inside-the-magic-pock... https://blo…
They moved most of their stuff away from AWS.