A service reads a newly written S3 object from a cross-Region replica immediately after the source write. Some reads miss the object briefly. What should the design account for?

Published
  1. Assume source read-after-write behavior forces immediate availability in every replica.
  2. Replication is asynchronous; define a suitable read path and replication-readiness behavior for the application consistency requirement.
  3. Disable source encryption to make every replica synchronous.
  4. Repeat the upload with new object names every time the replica is briefly behind.

Comments — 0