Blog

Your dream job? Lets Git IT.
Interactive technical interview preparation platform designed for modern developers.

XGitHub

Platform

  • Categories

Resources

  • Blog
  • About the app
  • FAQ
  • Feedback

Legal

  • Privacy Policy
  • Terms of Service

© 2025 LetsGit.IT. All rights reserved.

LetsGit.IT/Categories/Cloud
Cloudhard

Object storage consistency: why can you sometimes read stale data and how do you design for it?

Tags
#cloud#storage#consistency#eventual-consistency
Back to categoryPractice quiz

Answer

Depending on the provider and operation (especially overwrites and listings), object storage can behave like an eventually consistent system, so you may not see the newest state immediately. Design for it by avoiding overwrites (use unique keys/versioning), using retries with backoff, and not relying on immediate “list shows everything” semantics.

Related questions

Cloud
On‑demand vs reserved vs spot instances: what are the trade‑offs?
#cloud#pricing#on-demand
Cloud
Observability: how do metrics, logs, and traces differ?
#cloud#observability#metrics
Cloud
RTO vs RPO: what do these disaster‑recovery metrics mean?
#cloud#disaster-recovery#rto
Cloud
Stateless vs stateful services in the cloud: why does it matter?
#cloud#stateless#stateful
Cloud
Horizontal vs vertical scaling: what’s the difference?
#cloud#scaling#horizontal
Cloud
Blue/green vs canary deployments: what’s the difference?
#cloud#deployment#blue-green