I have been looking at some of the documentation for dynamodb best practices/design. Specifically Example of Modeling Relational Data in DynamoDB and Adjacency List Design Pattern.

I see in the above links that there are multiple types of partition keys in the table. For example in the second link it has an invoice-id and bill-id as partition keys. I am confused on how I create this type of schema when I go to create my table in AWS.

When I go to create DynamoDB table in the console I am given the option to have a table name, partition key and sort key. I do not see the ability to have an invoice-id and then separate bill-id partition key. Do I just keep the key names very generic and then within my application know that querying by key 1 is the invoice and key 2 is the bill?

I only have experience in relational databases and I see the above documentation, which makes sense and I seem to understand, but then I am having difficulty understanding how to put the Adjacency List Design Pattern into practice within dynamodb.



Found this right after posting, which explains what I am looking for pretty well

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.