Anyone have a good example of using @dynamodb with a single table and multiple entities? Having a hard time finding a good example. Most sample apps don't seem to use one table as recommended by #AWS as best practice.
-
-
For example, this video is spectacular, but it uses multiple tables for all of the application examples.https://www.youtube.com/watch?v=tDqLwzQEOmM …
1 reply 0 retweets 0 likesShow this thread -
Even the sample apps in the docs have multiple tables. https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/SampleData.CreateTables.html#SampleData.CreateTables1 …
1 reply 0 retweets 0 likesShow this thread -
Replying to @danbucholtz
Check out https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-adjacency-graphs.html … and https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-modeling-nosql-B.html …
3 replies 1 retweet 0 likes -
Replying to @southpolesteve
Say I wanted Users as a top level entity, the sort key could identify the individual user, but what is the partition key in that case? Do I hard-code it so I can query and page list of users? Otherwise how do I query top level stuff?
3 replies 0 retweets 0 likes
err more likely: partitionKey: "user:foo", sortKey: "user:foo". Kinda depends on if you want type scoping on stuff. If you want to paginate all users, you make a GSI on the sort key and query that
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.