Handling Large Blobs medium
S3 is now 'Strongly Consistent' (since 2020), but historically it was 'Eventual Consistent'. What did that mean?
- A It lost data occasionally.
- B If you PUT a new object, a robust system might immediately get a 404 on GET if the read hit a replica that hadn't received the write yet.
- C It was slow.
- D It only worked in US-East.
Answer: B. If you PUT a new object, a robust system might immediately get a 404 on GET if the read hit a replica that hadn't received the write yet.
Strong Consistency simplifies app logic. You no longer need to wait or check multiple times after a write.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- Why do modern sites serve images in WebP or AVIF format?
- What does the acronym BLOB stand for?
- Why do we sometimes convert binary images to Base64 strings?
- What is an 'Origin Shield' or 'Mid-Tier Cache' in a CDN architecture?
- For a feed with 100 images, why use 'Lazy Loading'?
- How does HLS/DASH handle a user moving from WiFi to 4G (Variable Bandwidth)?