Be still my beating heart. I have lived to see this day. Genuinely, we've wanted this for ages and we got half way there with strong consistency.
Might finally be possible to do this on S3:
https://pkg.go.dev/github.com/ncruces/go-gcp/gmutex
Amazon S3 Adds Put-If-Match (Compare-and-Swap)
11–20 of 166 posts
Re: Amazon S3 Adds Put-If-Match (Compare-and-Swap)
#12Be still my beating heart. I have lived to see this day. Genuinely, we've wanted this for ages and we got half way there with strong consistency.
So....given CAP, which one did they give up
Re: Amazon S3 Adds Put-If-Match (Compare-and-Swap)
#13If the default ETag algorithm for non-encrypted, non-multipart uploads in AWS is a plain MD5 hash, is this subject to failure for object data with MD5 collisions?
I'm thinking of a situation in which an application assumes that different (possibly adversarial) user-provided data will always generate a different ETag.
Re: Amazon S3 Adds Put-If-Match (Compare-and-Swap)
#14good example of how a simple feature on the surface (a header comparison) requires tremendous complexity and capacity on the backend.
Re: Amazon S3 Adds Put-If-Match (Compare-and-Swap)
#15First thing I thought when I saw the headline was "oh! I should tell Sirupsen"
Re: Amazon S3 Adds Put-If-Match (Compare-and-Swap)
#16Be still my beating heart. I have lived to see this day. Genuinely, we've wanted this for ages and we got half way there with strong consistency.
So....given CAP, which one did they give up
I’d wager that the algorithm is slightly eager to throw a consistency error if it’s unable to verify across partitions. Since the caller is naturally ready for this error, it’s likely not a problem. So in short it’s the P :)
Re: Amazon S3 Adds Put-If-Match (Compare-and-Swap)
#17good example of how a simple feature on the surface (a header comparison) requires tremendous complexity and capacity on the backend.
S3 is rated as "durable" as opposed to "best effort." It has lots of interesting guarantees as a result.
Re: Amazon S3 Adds Put-If-Match (Compare-and-Swap)
#18Earlier quoted context omitted.
So....given CAP, which one did they give up
I’d wager that the algorithm is slightly eager to throw a consistency error if it’s unable to verify across partitions. Since the caller is naturally ready for this error, it’s likely not a problem. So in short it’s the P :)
Shouldn't that be the A then? Since the network partition is still there but availability is non-guaranteed.
Re: Amazon S3 Adds Put-If-Match (Compare-and-Swap)
#19If the default ETag algorithm for non-encrypted, non-multipart uploads in AWS is a plain MD5 hash, is this subject to failure for object data with MD5 collisions? I'm thinking of a situation in which an application assumes that different (possibly adversarial) user-provided data will always generate a different ETag.
MD5 hash collisions are unlikely to happen at random. The defect was that you can make it happen purposefully, making it useless for security.
Re: Amazon S3 Adds Put-If-Match (Compare-and-Swap)
#20If the default ETag algorithm for non-encrypted, non-multipart uploads in AWS is a plain MD5 hash, is this subject to failure for object data with MD5 collisions? I'm thinking of a situation in which an application assumes that different (possibly adversarial) user-provided data will always generate a different ETag.
[deleted]