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 @danbucholtz
Those docs capture it, but need work. The gist is think of your single table as a list of edges. Nodes are just an edge that points to itself. All your relationships and indexes get jammed into your sort key.
1 reply 0 retweets 0 likes
Bustle had a lib that did something similar with two tables (nodes got their own table) https://github.com/bustle/dynamo-graph …. Not used anymore, but may be useful as a reference.
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.