hot key
A single key that receives a large share of all traffic, such as a celebrity account or a popular event.
In more detail
Hashing balances keys, not requests, so a hot key overloads its one partition while others sit idle. Remedies include salting reads across buckets, splitting the owner, replicating reads or queueing writes, and each changes ordering or the read path.
Related terms
- hot partition — A partition that gets far more traffic than the others because many requests use the same key, causing throttling even when total capacity is free.
- key salting — Adding a small random or computed suffix to a hot key so its load spreads over several partitions.
- skew — An uneven spread of data or traffic across partitions, so some do far more work than others.
Taught in
- Database Performance: Caches, Proxies And Capacity Units — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- The Performance Clinic: Five Slow Systems, Five Fixes — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- The Full Mock And Your Review Plan — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Partitioning, Sharding And Hot Keys — Scalable System Design & Distributed Architecture
- Cache Invalidation And The Three Hard Cases — Scalable System Design & Distributed Architecture
- The Difference Between A Queue And A Log — Scalable System Design & Distributed Architecture
- Load Balancing And The Failure Modes It Introduces — Scalable System Design & Distributed Architecture
- Worked Design One: Scaling The Ticket Booking System — Scalable System Design & Distributed Architecture
References
- Amazon DynamoDB: Designing partition keys to distribute your workload
- Google Cloud Bigtable: Schema design best practices