Dynamodb easy
What is the primary role of the 'Partition Key' in ensuring DynamoDB's infinite horizontal scalability?
- A It is used as a password for client-side authentication during the login phase.
- B It deterministically maps items to specific physical storage nodes via a hashing algorithm, ensuring that no single server becomes a bottleneck.
- C It defines the sorting order of the table for alphabetized exports.
- D It specifies which AWS Region the data should be stored in for lower latency.
Answer: B. It deterministically maps items to specific physical storage nodes via a hashing algorithm, ensuring that no single server becomes a bottleneck.
Horizontal scaling requires even distribution. DynamoDB hashes the partition key to select a 'Partition'. If your keys are diverse (e.g., `DeviceID`), your traffic is spread across many servers. If they are not (e.g., `ActiveStatus`), you create a 'Hot Partition' that throttles your throughut.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- DynamoDB has a strict 400KB limit on the size of a single item. What is the recommended design pattern if you need to store larger documents (e.g., 5MB PDFs)?
- Why is the `Query` operation generally preferred over `Scan` for production workloads in DynamoDB?
- DynamoDB is a 'fully managed' serverless database. What is a primary operational benefit of this model for an engineering team?
- In 'Provisioned Capacity' mode, how is the performance budget of a DynamoDB table defined?
- When would an architect choose to implement DAX (DynamoDB Accelerator) in front of an existing DynamoDB table?
- DynamoDB supports two types of Primary Keys. What is the fundamental difference between a 'Simple' and a 'Composite' primary key?