Live data from Hacker News

Dropbox traffic infrastructure: Edge network

blogs.dropbox.com

51–60 of 91 posts

Re: Dropbox traffic infrastructure: Edge network

#51
post #7

I wonder which definition of "Edge" is going to win out because right now it's being used interchangeably to mean either: 1) CDN or 2) On-premise machines/IoT.

This article is about neither of those things, though. https://en.m.wikipedia.org/wiki/Edge_device is the term that's relevant to this article. It's about the network edge itself.

Re: Dropbox traffic infrastructure: Edge network

#52

> DNS TTL is a lie. Even though we have TTL of one minute for www.dropbox.com, it still takes 15 minutes to drain 90% of traffic, and it may take a full hour to drain 95% of traffic. Interesting, awhile back both Google and AWS engineers replied to a HN thread[1] saying TTL of 30 seconds or so works pretty responsibly and can be trusted and used. Seems to be some disagreement on this. [1] https://news.ycombinator.com…

It would be funny if part of what they are seeing is because the Dropbox client doesn't try reconnects or re-resolving very often.

Re: Dropbox traffic infrastructure: Edge network

#53
post #45

Earlier quoted context omitted.

If you have trouble to connect to github.com how you're going to "git clone https://github.com/[xxx]" ?

Because it's possible that you can't clone from the https endpoint but you can from the git endpoint, which helps them (and you) debug the cause.

Yeah, but then the last step is to "copy & paste the results" to .. https://github.com/contact

Re: Dropbox traffic infrastructure: Edge network

#54
post #35
post #25

Earlier quoted context omitted.

That's an interesting implication. If they distribute the same cert so widely geographically, any host country could technically request it for "lawful intercepts".

A host country can request a lawful intercept regardless of whatever technical conditions exist on your network.

[deleted]

Re: Dropbox traffic infrastructure: Edge network

#55
post #37

Earlier quoted context omitted.

I'm also curious how torrents are used and why.

I would guess that they do something similar to Facebook. Ars covered what Facebook do about 6 years ago, and even then I think they'd been using it for a few years: https://arstechnica.com/information-technology/2012/04/exclu... I believe Twitter does something similar too.

MSN Hotmail and Messenger used torrents to distribute binaries in 2006. It's not new nor novel.

And I'm sure someone did it before they did.

Re: Dropbox traffic infrastructure: Edge network

#56
post #45

Earlier quoted context omitted.

Because it's possible that you can't clone from the https endpoint but you can from the git endpoint, which helps them (and you) debug the cause.

Yeah, but then the last step is to "copy & paste the results" to .. https://github.com/contact

I'm assuming it also logs some debugging information with regards to your git client's behavior, though. So you could still be able to get to that contact form.

Re: Dropbox traffic infrastructure: Edge network

#57

> DNS TTL is a lie. Even though we have TTL of one minute for www.dropbox.com, it still takes 15 minutes to drain 90% of traffic, and it may take a full hour to drain 95% of traffic. Interesting, awhile back both Google and AWS engineers replied to a HN thread[1] saying TTL of 30 seconds or so works pretty responsibly and can be trusted and used. Seems to be some disagreement on this. [1] https://news.ycombinator.com…

It really depends on the clients, here is an excerpt from the article: > Here we also need to mention the myriad embedded devices using Dropbox API that range from video cameras to smart fridges which have a tendency of resolving DNS addresses only during power-on.

> which have a tendency of resolving DNS addresses only during power-on.

Facepalm...

Re: Dropbox traffic infrastructure: Edge network

#58
post #46
post #14

Earlier quoted context omitted.

I've never heard it used with that second definition. It's pretty consistently used to refer to running close to the user, as opposed to having a big data center which most of your users aren't near. The second definition could be a confusion of ownership — i.e. are you paying a CDN to do higher-level service or running the services yourself?

I work on an Edge Platform team as part of an Edge Foundation that manages both external CDN and internal Tier 1 WAF/Ingress systems. We do Edge computing at both CDN and Tier 1 layers via tenant plugins running LUA/go. We also have an SDN team building Tier 2 solutions, so basically systems operating at the edge of each layer of the HTTP stack.

And let me guess, the web admin dashboard only works in ... IE6?

Re: Dropbox traffic infrastructure: Edge network

#59
post #55

Earlier quoted context omitted.

I would guess that they do something similar to Facebook. Ars covered what Facebook do about 6 years ago, and even then I think they'd been using it for a few years: https://arstechnica.com/information-technology/2012/04/exclu... I believe Twitter does something similar too.

MSN Hotmail and Messenger used torrents to distribute binaries in 2006. It's not new nor novel. And I'm sure someone did it before they did.

What binaries did MSN Hotmail have? It was the earlier web mail incarnation of outlook.com?

Re: Dropbox traffic infrastructure: Edge network

#60

> DNS TTL is a lie. Even though we have TTL of one minute for www.dropbox.com, it still takes 15 minutes to drain 90% of traffic, and it may take a full hour to drain 95% of traffic. Interesting, awhile back both Google and AWS engineers replied to a HN thread[1] saying TTL of 30 seconds or so works pretty responsibly and can be trusted and used. Seems to be some disagreement on this. [1] https://news.ycombinator.com…

DNS TTL is a PITA for us at Netflix as well. We use Zuul to proxy cross-region for TTL "non-responders".
Post reply on HN