This website uses cookies to ensure you get the best experience.
Learn more.
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
- Assume source read-after-write behavior forces immediate availability in every replica.
- Replication is asynchronous; define a suitable read path and replication-readiness behavior for the application consistency requirement.
- Disable source encryption to make every replica synchronous.
- Repeat the upload with new object names every time the replica is briefly behind.
Comments — 0
Sign in to comment