Document the consistency model #289
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#289
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
After reading the design goals [1] and benchmark [2], I'm curious about the consistency model. It's obvious that you are using a quite weak consistency model to get better performance, but this model is not described in details. I would expect that description to be part of the design goals, it's quite important to know what can be expected from garage.
I did find a bit more details (in French) in these slides [3] but it's still very high-level.
[1] https://garagehq.deuxfleurs.fr/documentation/design/goals/
[2] https://garagehq.deuxfleurs.fr/documentation/design/benchmarks/
[3] https://git.deuxfleurs.fr/Deuxfleurs/garage/src/branch/main/doc/talks/2020-12-02_wide-team/talk.pdf
Garage Consistency Model for the S3 API is the same as Amazon's New Strong-Consistency Model, ie. Read Your Write. You can find more details here: https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html#ConsistencyModel
Considering the admin's API, it has a weaker consistency compared to S3. We plan to define it more precisely soon.