IBM Cloud Object Storage - 什么是数据一致性/可见性模型？
IBM Cloud Object Storage - what is the data consistency / visibility model?
IBM 的 Cloud Object Storage 在数据一致性/可见性方面提供什么保证？ AWS 基本上是新对象的先写后读，updates/deletes 的最终一致性。那么，IBM COS 的数据一致性模型是怎样的呢？而且，我怀疑是否支持对象锁定，但想验证它确实是不可能的（如果是的话会很棒！）。
作为参考，AWS 声明了他们的数据一致性模型 here:
Amazon S3 provides read-after-write consistency for PUTS of new objects in your S3 bucket in all regions with one caveat. The caveat is that if you make a HEAD or GET request to the key name (to find if the object exists) before creating the object, Amazon S3 provides eventual consistency for read-after-write.
Amazon S3 offers eventual consistency for overwrite PUTS and DELETES in all regions.
Updates to a single key are atomic. For example, if you PUT to an existing key, a subsequent read might return the old data or the updated data, but it will never write corrupted or partial data.
关于对象锁定：
Amazon S3 does not currently support object locking. If two PUT requests are simultaneously made to the same key, the request with the latest time stamp wins. If this is an issue, you will need to build an object-locking mechanism into your application.
Updates are key-based; there is no way to make atomic updates across keys. For example, you cannot make the update of one key dependent on the update of another key unless you design this functionality into your application.
IBM COS 对所有操作立即保持一致，但与 AWS 一样，此时不支持对象锁定。
我正在写一篇文章，我们将把它折叠到我们的文档中，内容是关于我们的一致性模型及其工作方式的原因，敬请期待！
IBM 的 Cloud Object Storage 在数据一致性/可见性方面提供什么保证？ AWS 基本上是新对象的先写后读，updates/deletes 的最终一致性。那么，IBM COS 的数据一致性模型是怎样的呢？而且，我怀疑是否支持对象锁定，但想验证它确实是不可能的（如果是的话会很棒！）。
作为参考，AWS 声明了他们的数据一致性模型 here:
Amazon S3 provides read-after-write consistency for PUTS of new objects in your S3 bucket in all regions with one caveat. The caveat is that if you make a HEAD or GET request to the key name (to find if the object exists) before creating the object, Amazon S3 provides eventual consistency for read-after-write.
Amazon S3 offers eventual consistency for overwrite PUTS and DELETES in all regions.
Updates to a single key are atomic. For example, if you PUT to an existing key, a subsequent read might return the old data or the updated data, but it will never write corrupted or partial data.
关于对象锁定：
Amazon S3 does not currently support object locking. If two PUT requests are simultaneously made to the same key, the request with the latest time stamp wins. If this is an issue, you will need to build an object-locking mechanism into your application.
Updates are key-based; there is no way to make atomic updates across keys. For example, you cannot make the update of one key dependent on the update of another key unless you design this functionality into your application.
IBM COS 对所有操作立即保持一致，但与 AWS 一样，此时不支持对象锁定。
我正在写一篇文章，我们将把它折叠到我们的文档中，内容是关于我们的一致性模型及其工作方式的原因，敬请期待！