durability
The likelihood that stored data survives hardware failures without being lost, usually stated as a percentage per year.
In more detail
S3 is designed for 99.999999999 per cent (eleven nines) durability by keeping copies across availability zones. Durability is not the same as availability or backup: a durable store keeps a mistaken delete or a corrupted write just as reliably.
Related terms
- availability — The share of time, or of requests, in which a service works for the people who need it, often written as a percentage such as 99.9 per cent.
- replication — Keeping copies of data in more than one place, updated automatically, so one failure does not lose or block it.
- backup and restore — Keeping recoverable copies of data from past points in time, and being able to bring them back.
- consistency — The guarantee about whether what you read reflects what was most recently written.
- replication factor — The number of copies of each piece of data a system keeps, commonly three.
- write behind — A caching strategy that writes to the cache first and copies the data to the database later.
Taught in
- Technology Sprint: The Design Review — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- Storage Performance: IOPS, Throughput And The Right Volume — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Storage Cost: Classes, Lifecycle Rules And The Retrieval Trap — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Network Cost: NAT Gateways, Zones And Data Out — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- The Shared Responsibility Model — Cloud Infrastructure & Hyperscaler Architecture
- The Danger of Long-Lived Keys — Cloud Infrastructure & Hyperscaler Architecture
- Elastic Compute Cloud (EC2) — Cloud Infrastructure & Hyperscaler Architecture
- Object, Block, and File Storage — Cloud Infrastructure & Hyperscaler Architecture
- Elastic Block Store (EBS) — Cloud Infrastructure & Hyperscaler Architecture
- NoSQL and DynamoDB — Cloud Infrastructure & Hyperscaler Architecture
- The Console versus the CLI — Cloud Infrastructure & Hyperscaler Architecture
- Requirements: The Constraints That Shape The System — Scalable System Design & Distributed Architecture
- Back Of The Envelope Estimation: Storage And Bandwidth — Scalable System Design & Distributed Architecture
- The Storage Decision: Key Value, Search And Blob — Scalable System Design & Distributed Architecture
- Replication, Failover And Leader Election — Scalable System Design & Distributed Architecture
- Consistency, And The Truth About CAP — Scalable System Design & Distributed Architecture
- Eventual Consistency And What It Costs A Product — Scalable System Design & Distributed Architecture
- Idempotency, And Exactly Once As A Fiction — Scalable System Design & Distributed Architecture
- Worked Design Two: A Global Chat System — Scalable System Design & Distributed Architecture
- Worked Design Two: Scaling Chat Fan Out — Scalable System Design & Distributed Architecture
- Worked Design Three: A Metrics Ingestion Pipeline — Scalable System Design & Distributed Architecture
- Worked Design Three: Scaling The Metrics Pipeline — Scalable System Design & Distributed Architecture
References
- Data protection in Amazon S3
- Google SRE book: Managing Critical State
- AWS Well-Architected Framework: Reliability Pillar