You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I kindly request reconsideration of implementing the previously rejected feature discussed in Issue #1085. The original feature request was declined due to plans to integrate a Data Mapper in TypeORM, which have since been abandoned by the TypeORM team. This decision leaves current Data Mapper users without a viable alternative.
Use Case
In my project, we're using the awslabs dynamodb data mapper across multiple services. However, its lack of support for AWS SDK v3 is problematic, especially considering that alternative solutions are either not widely adopted, have bloated dependency trees making maintenance challenging, or are unsuitable for specific runtimes such as AWS Lambda.
DDM Is a light, purpose-built solution that works extremely well and we didn't have any issues using it for many years already. if it would be only possible we would love to continue using it.
Proposed Solution
I propose incorporating DynamoDB Data Mapper into the AWS SDK, similar to the Java version. This integration would provide a stable, well-maintained solution for the JavaScript/TypeScript community, aligning with the needs of many developers currently using the awslabs DynamoDB Data Mapper.
I see two main issues with typeorm-dynamodb compared to the dynamodb data mapper
larger dependency tree
lower adoption - 83 vs 21,548 weekly downloads
The DynamoDB Data Mapper remains popular and widely used. It is battle-tested and has a smaller dependency tree, making it easier to maintain and more suitable for certain runtimes such as lambda.
Describe the feature
I kindly request reconsideration of implementing the previously rejected feature discussed in Issue #1085. The original feature request was declined due to plans to integrate a Data Mapper in TypeORM, which have since been abandoned by the TypeORM team. This decision leaves current Data Mapper users without a viable alternative.
Use Case
In my project, we're using the awslabs dynamodb data mapper across multiple services. However, its lack of support for AWS SDK v3 is problematic, especially considering that alternative solutions are either not widely adopted, have bloated dependency trees making maintenance challenging, or are unsuitable for specific runtimes such as AWS Lambda.
DDM Is a light, purpose-built solution that works extremely well and we didn't have any issues using it for many years already. if it would be only possible we would love to continue using it.
Proposed Solution
I propose incorporating DynamoDB Data Mapper into the AWS SDK, similar to the Java version. This integration would provide a stable, well-maintained solution for the JavaScript/TypeScript community, aligning with the needs of many developers currently using the awslabs DynamoDB Data Mapper.
Other Information
Acknowledgements
SDK version used
v3
Environment details (OS name and version, etc.)
any
The text was updated successfully, but these errors were encountered: