Dynamoose is a modeling tool for Amazon's DynamoDB github.com/dynamoose/dynamoo…

Joined March 2020
2 Photos and videos
21 Apr 2023
Dynamoose has officially hit 100k weekly downloads for the first time ever! Thanks to everyone in the community who has supported the project. 🎉
99
20 Jul 2022
Introduction to Dynamoose video course is now available! Lots of great video lessons about the basics of Dynamoose for only $9.99. learn.rrainn.com/courses/dd4…
1
1
15 Jan 2022
Dynamoose v3 has been promoted to beta status 🎉. Try it out today and submit any feedback to our @GitHub repo! github.com/dynamoose/dynamoo…
1
18 Dec 2021
Super cool to see @DynamooseJS on @24PullRequests!! 🎉 Thanks to everyone who has contributed to @DynamooseJS over the years. ❤️ If you are interested in contributing and need assistance feel free to join our Slack room to ask questions. Many more improvements to come!!
1
3
Dynamoose retweeted
Ever curious what the difference is between @dynamodb On-Demand Scaling and Provisioned with Auto-Scaling? Well look no further. I just wrote a guest article for @dynobase going over this exact topic! dynobase.dev/dynamodb-on-dem…
1
2
Dynamoose retweeted
13 May 2021
If you miss models, schemas, and other things from ORM approach in DynamoDB world, try Dynamoose. It's heavily inspired by Mongoose, supports types, transactions and strict data modelling. github.com/dynamoose/dynamoo…
3
14
Dynamoose retweeted
Remember to support your favourite OSS projects! As @dynobase, we're happy supporters (and users) of @DynamooseJS opencollective.com/dynamoose
1
2
6
22 Feb 2021
For the past 14 days we have worked to get the @DynamooseJS vulnerability (github.com/dynamoose/dynamoo…) added to the @npmjs audit feature with no success. There is no documentation or information about how to get vulnerabilities added to their DB.
2
1
2
22 Feb 2021
We would also like to thank @snyksec for replying to us in a very timely manner and adding this vulnerability to their database.
1
1
2
22 Feb 2021
This has now been resolved. Thank you to the @npmjs team for addressing this. npmjs.com/advisories/1610

1
2