access pattern
How an application actually reads and writes its data: how often, how much, by which key and how quickly it needs answers.
In more detail
Access patterns should choose the storage shape, the storage tier and, in DynamoDB, the keys. Measure them rather than guess, for example from request metrics or logs.
Related terms
- S3 storage class — The S3 price and speed level an object is stored at, from Standard for frequent access to Glacier archive tiers for rarely read data.
- partition key — The DynamoDB attribute whose value decides which storage partition an item lives in, and which every query must name.
- object storage — Cloud storage that keeps whole files, called objects, in buckets and serves them over the network, such as Amazon S3.
- workload table — A table listing each entity with its hottest read, write rate, size and the invariant it must keep, used to choose storage.
- key-value store — A database that stores each item under a unique key and fetches it by that key, very quickly and at large scale.
Taught in
- One Database Doing Five Jobs — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- Ten Terabytes Nobody Reads — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- Load Balancers And Auto Scaling: Capacity That Arrives On Time — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- 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
- Storage Cost: Classes, Lifecycle Rules And The Retrieval Trap — 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
- Comparing Compute Options — Cloud Infrastructure & Hyperscaler Architecture
- Object, Block, and File Storage — Cloud Infrastructure & Hyperscaler Architecture
- S3: Permissions, Tiers, and Policies — Cloud Infrastructure & Hyperscaler Architecture
- NoSQL and DynamoDB — Cloud Infrastructure & Hyperscaler Architecture
- The Storage Decision: Relational Versus Document — Scalable System Design & Distributed Architecture
- The Storage Decision: Key Value, Search And Blob — Scalable System Design & Distributed Architecture
- Partitioning, Sharding And Hot Keys — Scalable System Design & Distributed Architecture
References
- DynamoDB: identify your data access patterns
- Amazon DynamoDB: Designing partition keys to distribute your workload