11–20 of 91 posts
Would be great to know how exactly they store all the customer data on this edge network. Is it encrypted with a customer-specific key? If yes, when and how do they decrypt it?
I'm surprised there is no mention of security or privacy. I'd have thought that's one of the reasons for controlling your own edge network.
Who would have thought a simple FTP-on-some-server would have been so complicated. Thanks for the post! I'm eagerly waiting for the blog post about how bazel and torrents are used.
Who describes Dropbox as the same as FTP?
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.
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?
Earlier quoted context omitted.
Who describes Dropbox as the same as FTP?
Cynical HN commenters from a decade ago. It's pretty hilarious in retrospect.
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.
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?
Wikipedia's definition primarily focuses on the local/IoT version as a distinctly different from utilizing a CDN.
Would be great to know how exactly they store all the customer data on this edge network. Is it encrypted with a customer-specific key? If yes, when and how do they decrypt it?
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.
> 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…