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.
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.
-
-
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.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.