Hey Dina, thanks for the comment and sorry I haven't got back to you sooner!
I think Dynamoose is popular because it's basically the only thing out there attempting to do something like this. I don't think Dynamoose is bad, it's cool and it has a lot of functionality, but it just wasn't what I was looking for.
I think the big advantages Jedlik has over Dynamoose are firstly that it's simpler and more lightweight, and second, that it supports single-table design - you can have multiple models that read and write from the same table, which is an important feature of DynamoDB.
Also Dynamoose is based on Mongoose, but MongoDB and DynamoDB are completely different so I wanted to do something that still feels more like you're using DynamoDB, not like you're pretending to use MongoDB.
I wrote Jedlik out of frustration with using the AWS SDK for DynamoDB, specifically around how cumbersome and verbose it is to use, how full of non-generic terminology it is (AttributeValueNames???), and how there's basically no validation when writing data. Those are the problems that I'm trying to solve - to give you a more intuitive interface, and a bit of data validation. Otherwise, it should be similar to using DynamoDB normally.
In terms of is it production ready... I'm using it in production at work and it works great! It's well tested too - the codebase contains a tonne of unit tests, and integration tests with DynamoDB local, if you want to check those out!
Thanks a lot for the response. I will continue to try jedlik in future. I made some comments on repository github.com/peak-ai/jedlik/issues/22. May be enabling source map would fix that problem.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey Dina, thanks for the comment and sorry I haven't got back to you sooner!
I think Dynamoose is popular because it's basically the only thing out there attempting to do something like this. I don't think Dynamoose is bad, it's cool and it has a lot of functionality, but it just wasn't what I was looking for.
I think the big advantages Jedlik has over Dynamoose are firstly that it's simpler and more lightweight, and second, that it supports single-table design - you can have multiple models that read and write from the same table, which is an important feature of DynamoDB.
Also Dynamoose is based on Mongoose, but MongoDB and DynamoDB are completely different so I wanted to do something that still feels more like you're using DynamoDB, not like you're pretending to use MongoDB.
I wrote Jedlik out of frustration with using the AWS SDK for DynamoDB, specifically around how cumbersome and verbose it is to use, how full of non-generic terminology it is (AttributeValueNames???), and how there's basically no validation when writing data. Those are the problems that I'm trying to solve - to give you a more intuitive interface, and a bit of data validation. Otherwise, it should be similar to using DynamoDB normally.
In terms of is it production ready... I'm using it in production at work and it works great! It's well tested too - the codebase contains a tonne of unit tests, and integration tests with DynamoDB local, if you want to check those out!
I've also made a demo repository if you'd like examples - github.com/harrim91/jedlik-demo
Thanks a lot for the response. I will continue to try jedlik in future. I made some comments on repository github.com/peak-ai/jedlik/issues/22. May be enabling source map would fix that problem.