Live data from Hacker News

Amazon S3’s 15th Birthday: 5,475 Days and 100T Objects

aws.amazon.com

71–79 of 79 posts

Re: Amazon S3’s 15th Birthday: 5,475 Days and 100T Objects

#71
post #70

Earlier quoted context omitted.

... this is on you to prove it is their secret sauce. Throwing out some random feature and saying it is their secret sauce and putting the burden of proof on somebody else makes no sense. But it would be because 1) they probably don't have many duped objects to begin with 2) the system to de-dupe items would be complex, error prone, increase latency, and just not worth it

> 1) they probably don't have many duped objects to begin with That's crap reasoning. You have no way of knowing that. > 2) the system to de-dupe items would be complex, error prone, increase latency, and just not worth Would it really be that complex? I kinda doubt that. Read latencies wouldn't be affected - except being improved. Write latencies - the deduplication can happen after the write has been confirmed, so…

It's like you are living in an alternate reality

Re: Amazon S3’s 15th Birthday: 5,475 Days and 100T Objects

#72
post #70

Earlier quoted context omitted.

> 1) they probably don't have many duped objects to begin with That's crap reasoning. You have no way of knowing that. > 2) the system to de-dupe items would be complex, error prone, increase latency, and just not worth Would it really be that complex? I kinda doubt that. Read latencies wouldn't be affected - except being improved. Write latencies - the deduplication can happen after the write has been confirmed, so…

It's like you are living in an alternate reality

...because?

I dunno, I kinda think you might be out of your depth on this one, based on that response.

Also: none of your few previous posts are tech-related. They're all about personal finance.

Re: Amazon S3’s 15th Birthday: 5,475 Days and 100T Objects

#73
post #72

Earlier quoted context omitted.

It's like you are living in an alternate reality

...because? I dunno, I kinda think you might be out of your depth on this one, based on that response. Also: none of your few previous posts are tech-related. They're all about personal finance.

So just to sum up your argument: You think 33% of objects in S3 are dupes and that removing those dupes would be S3's secret sauce?

Re: Amazon S3’s 15th Birthday: 5,475 Days and 100T Objects

#74
post #9

I am really getting afraid of this centralization of data.

I think it’s fine as long as people know what they’re getting themselves into. I’m sure I would’ve found whatever was happening on Parler abhorrent, but in the same way Merkel and Macron were concerned by the tech deplatforming that followed the capitol riots, so am I.

I don’t think filecoin will ever demolish a fantastic business like S3 based on stealing away customers. The interesting value proposition from the protocol is probably more about censorship resistance and adjacent issues.

Re: Amazon S3’s 15th Birthday: 5,475 Days and 100T Objects

#75
post #72

Earlier quoted context omitted.

...because? I dunno, I kinda think you might be out of your depth on this one, based on that response. Also: none of your few previous posts are tech-related. They're all about personal finance.

So just to sum up your argument: You think 33% of objects in S3 are dupes and that removing those dupes would be S3's secret sauce?

Congratulations on being able to do 6th grade math.

Re: Amazon S3’s 15th Birthday: 5,475 Days and 100T Objects

#76
post #75

Earlier quoted context omitted.

So just to sum up your argument: You think 33% of objects in S3 are dupes and that removing those dupes would be S3's secret sauce?

Congratulations on being able to do 6th grade math.

You're incredibly condescending and just full of incorrect assumptions. Done with this conversation

Re: Amazon S3’s 15th Birthday: 5,475 Days and 100T Objects

#79

I wonder how much of ceph inspired s3...

Very little, I'm sure. S3 and Ceph were both introduced to the world in 2006, which means they had been in development at the same time - or perhaps S3 even a bit before, since it was in a far more mature state by then. Also, while S3 and Ceph's RADOS both supposedly handle "objects" they're very different kinds of objects with very different APIs. And of course the metadata layers are completely different to serve different needs. It's practically certain that they both drew on the same common ancestors, but it's more likely that lessons learned from S3 informed subsequent development on Ceph than the other way around.
Post reply on HN