Consistency guarantees?

[bjorn3]

If the blob store is used in a distributed system what consistency guarantees does a wasi-blobstore implementation need to guarantee to be considered an implementation conforming to this specification? For example:

• Is a client guaranteed to read the data it has previously written (if there is no later write by another client)?
• Is there any ordering guarantee between reads/writes within a single container? (so eg if you have a program which creates a new object and after that updates an index in another object referencing the newly created object is a concurrent reader guaranteed to be able to read the new object once the index contains a reference to the new object)
• ...

See also https://en.wikipedia.org/wiki/Consistency_model for a whole bunch of consistency guarantees. And https://jepsen.io/ for a whole lot of testing of distributed systems where many are shown to fail even on their documented consistency guarantees.

[bjorn3]

Something somewhat related: Should timestamps be guaranteed to be monotonic with respect to the order in which the object store received the object creation request or are clock adjustments due to time synchronization allowed or because the object store itself consists of multiple machines with slightly different clocks?