61–70 of 158 posts
Earlier quoted context omitted.
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.
Is 500 petabytes really that epic? 1500 tapes? I could probably stuff that in the back of my minivan.
Granted, I stopped paying attention to tape drive capacities a while ago, but the upcoming LTO-8 standard will "only" support 13TB/tape, so you'd need 38,000 of them to hold 500 PB.
I've seen some higher density announcements in the 200 - 300TB/tape range, but couldn't find any products available.
AWS does offer a "Snowmobile" [1] product, that can hold 100PB on disks in a tractor trailer.
[1] https://aws.amazon.com/blogs/aws/aws-snowmobile-move-exabyte...
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"
So the solution is SO bad that the "amp" tag even becomes part of the URL?!
Now THAT is really weird ... well aside from me disliking AMP anyway, that ... hmmm. We can send people to the moon, probably soon elswhere but ... we have to denote that ... we use AMP by ... a appended string called 'amp'.
Google should be ashamed of this "engineering".
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?
So OTHERS made a new decision for YOU - as the visitor.
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"
Oh wow, I did not even notice this until you pointed it out. So the solution is SO bad that the "amp" tag even becomes part of the URL?! Now THAT is really weird ... well aside from me disliking AMP anyway, that ... hmmm. We can send people to the moon, probably soon elswhere but ... we have to denote that ... we use AMP by ... a appended string called 'amp'. Google should be ashamed of this "engineering".
Dropbox 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
In this post they say specifically it is about the handshake:
https://blogs.dropbox.com/tech/2017/06/evolution-of-dropboxs...
I don't know if they use SSL/TLS to their upstreams, I'm just saying terminating in at the edge doesn't mean that is the end of all SSL/TLS. It is totally normal to terminate SSL/TLS at the edge, pretty much anyone using an HTTPS load balancer or CDN does it, but the LB or CDN can still use SSL/TLS to the upstreams and verify certificates of upstreams.
"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?
1500 sounds like a lot, but keep in mind how many customers they have, and in how many countries they sell their services.
Dropbox 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
> We use TLS 1.2 and a PFS cipher suite at both our origin data centers and proxies. Additionally, we’ve enabled upstream certificate validation and certificate pinning on our proxy servers. This helps ensure that the edge proxy server knows it’s talking to our upstream server, and not someone attempting a man-in-the-middle attack.
(N.B.: I work on security at Dropbox, and consulted on this design)
[1]: https://blogs.dropbox.com/tech/2016/11/infrastructure-update...