---
title: "Case: Amazon Dynamo, the paper"
description: "What Amazon's 2007 Dynamo paper says about staying writable during failures, what happens when two copies accept different versions, and what came after."
canonical_url: "https://fanout.sh/system/archive/case-amazon-dynamo"
md_url: "https://fanout.sh/system/archive/case-amazon-dynamo.md"
last_updated: "2026-11-11"
access: "pro-preview"
---

# Case: Amazon Dynamo, the paper

What Amazon's 2007 Dynamo paper says about staying writable during failures, what happens when two copies accept different versions, and what came after.

- Access: Fanout Pro (public preview)

## The core idea

Dynamo was Amazon's internal key-value store for services that needed to keep accepting useful work during failures.

Its 2007 paper is especially useful for understanding what happens after two parts of a system accept different versions of an object.

## In this lesson

- What they had
- What broke, or would not scale
- The numbers they published
- The decision
- What changed after
- Fundamentals used

## Continue reading

Pro unlocks video lessons, visual walkthroughs, full notes, diagrams, case studies, and implementations across the System Design archive.

---
This representation contains public Fanout content only. Protected Pro lessons, account data, billing, checkout, and pricing are not included.

Browse the public content map: https://fanout.sh/sitemap.md
