shiftcode/dynamo-easy

DAX support

Closed this issue · 5 comments

joeyhotz commented

Do you allow users to modify the dynamodb client used by dynamo easy? I want to be open to using DAX in the future and I'm not sure if this is supported from looking at the docs.

ali-habibzadeh commented

Ideal updateDynamoEasyConfig would have an additional field where we can pass client into and since Dax and Dynamodb have the same api, it shouldn't cause architecture change for dynamo-easy, besides abstracting out the underlying client used. Currently they are hardcoded inside dynamo services like import * as DynamoDB from 'aws-sdk/clients/dynamodb'.

However it shouldn't be a global setting only as most likely applications will consist of both tables that directly use Dynamodb client and tables assiciated with a dax cluster.

@joeyhotz in the meantime, if you don't have specific need for using the Transactions API then you can use https://github.com/awslabs/dynamodb-data-mapper-js which does support decorators like this but is also flexible in terms of taking client as an argument.

simonmumenthaler commented

hi @joeyhotz @ali-habibzadeh
I never worked with the DAX client - but:
The DynamoStore constructor takes as the second argument an optional DynamoDB client instance. So if the API from DAX is compatible it should already work. (Also every non-store request class (eg. BatchGetRequest) accepts an optional dynamoDB client)

I'd be nice if you could evaluate this :)

  • 👍2
itsdarrylnorris commented

Hey @joeyhotz,

Any luck running DAX? I am considering using DAX on a project that I am working on right now.

joeyhotz commented
michaelwittwer commented

closing this in favour of #374 holding relevant topics to be updated in the docs, serving as a knowledge base for now and also describing the strategy of the technical solution of the documentation part, envision it to be closer to the source code of the project