Skip to content

Latest commit

 

History

History
23 lines (16 loc) · 1.87 KB

dynamodb.md

File metadata and controls

23 lines (16 loc) · 1.87 KB
Raw

This page tries to cover many aspects of choosing DynamoDB as the storage solution and tries to provide hints and guidance about the technology.

Is it the right tool for you?

You have to consider many aspects which are described in this post, but overall, if you can’t predict your access patterns or are likely to change frequently, you need to run ad hoc queries on your data, then probably DynamoDB is not the best tool for you.

Designing for NoSQL

You should clearly understand your relational schema (all data is relational), and starting from the relational model, denormalize it into one or two tables fulfilling your access patterns. Some resources to get started:

  1. Data modeling (part 1)
  2. Data modeling (part 2)
  3. Advanced design patterns (part 1)
  4. Advanced design patterns (part 2)
  5. The What, Why, and When of Single-Table Design
  6. How DynamoDB scales where relational databases don't

Examples of Modeling Relational Data in DynamoDB

  1. Example of modeling relational data in DynamoDB
  2. Instagram model from Alex DeBrie, with code https://github.com/alexdebrie/dynamodb-instagram#readme"

Dive deep

  1. https://github.com/papers-we-love/papers-we-love/blob/master/datastores/dynamo-amazons-highly-available-key-value-store.pdf