Current status

[lyxsus]

What is current status of this project? Couldn't find any live fork or successor or alternative.

[aaaristo]

It is not maintained: nowadays I'm mostly using plain dynamo (aws-sdk with DocumentClient: http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/DynamoDB/DocumentClient.html ).

On Sun, 30 Jul 2017 at 06:00, Sergey Antoninko notifications@github.com wrote:

What is current status of this project? Couldn't find any live fork or successor or alternative.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/aaaristo/dyngodb/issues/20, or mute the thread https://github.com/notifications/unsubscribe-auth/AARPmGhlAEuJtSgxwlBKawIL0mdV8EWuks5sS7mkgaJpZM4OnfHg .

-- Andrea Gariboldi, Technical Screener || Toptal || andrea.gariboldi (skype)

[lyxsus]

Yeah. It feels weird that documentClient is the only production-ready option for dynamodb+node for that many years. I understand, why regular ORM-like solutions didn't work, but it must be possible to have something of higher level than this. For example, Titan with dynamodb looked good, but I don't want to run an instance for such things and I saw no attempts to do some stateless language-agnostic protocol for that.

dyngodb was a very interesting idea in that sense. What stopped you?

[aaaristo]

This was one thing: https://github.com/awslabs/dynamodb-transactions/issues/3

I reimplemented the protocol from scratch in dyngo but at the end of the exercise I think the entire project should be refactored with async / await + better coding standards and probably having a proper port of dynamodb-transactions via:

https://github.com/cincheo/jsweet/issues/388

I simply do not have enough time to bring this forward now.