I get that. Similar setup myself. I have yet to find a good abstraction for dealing with Dynamo.
-
-
Replying to @southpolesteve @brianleroux
I think DocumentClient is as far as I'd go – anything more and you're getting into magic territory IMO http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/DynamoDB/DocumentClient.html …
2 replies 0 retweets 1 like -
Gotta say though, if you're hooking it up to GraphQL, then it's hard to beat Redis
2 replies 0 retweets 1 like -
(or did you mean, like, an in-process DB specifically?)
1 reply 0 retweets 0 likes -
Replying to @hichaelmart @brianleroux
Looking like this is going to end up as a bunch of json files. Who needs a database??
1 reply 0 retweets 1 like -
Replying to @southpolesteve @brianleroux
Heh, I mean, if it really is just read-only, then, yeah... Could even make it a bunch of JS files and save some quotation marks
3 replies 0 retweets 0 likes -
Replying to @hichaelmart @brianleroux
This will be open source prob by end of weekend. Ya'll can see how the sausage gets made.
1 reply 0 retweets 1 like -
1 reply 0 retweets 1 like
-
Replying to @southpolesteve @brianleroux
Seems to be down at the mo, but looks nice! Could setup an index (map) on ObjectID to speed up `data.find` queries too (if they're slow?)
1 reply 0 retweets 0 likes -
Replying to @hichaelmart @brianleroux
yeah appears a complex query can take it down. Needs some tweaks!
1 reply 0 retweets 0 likes
good suggestion. that map(find(id)) call was not helping https://github.com/southpolesteve/pma-graph/commit/0279fd2e3febfe6f25f4b8ac7c77b5e3b0fd084e …
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.