search

storj / roadmap

Storj Public Roadmap
Other
11 stars 4 forks source link

Remaining strong consistency cleanup #31

Closed jtolio closed 3 months ago

jtolio commented 2 years ago

After https://github.com/storj/roadmap/issues/18 is done, we need to make sure we can declare success and market strong consistency across our product. #18 should be sufficient, but we need to confirm.

Acceptance criteria: all Uplink operations provide at least strong read-after-write consistency (https://aws.amazon.com/blogs/aws/amazon-s3-update-strong-read-after-write-consistency/), but it would be better to be higher up on https://jepsen.io/consistency.

mniewrzal commented 1 year ago

@jt @onionjake looking at https://jepsen.io/consistency did we have in mind any specific level of consistency? or we should try to achieve highest Strict Serializability consistency level.

onionjake commented 1 year ago

@mniewrzal We don't need to provide any more guarantees than the underlying metainfo database, so CRDB's default consistency. Additionally, the guarantees for our product are only for object operations, not bucket or otherwise.

In practice this means we need to make sure we are appropriately using transactions on all operations.

iglesiasbrandon commented 1 year ago

global milestone: https://github.com/storj/storj/milestone/28

iglesiasbrandon commented 3 months ago

closing this issue until it becomes more relevant.