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
{{ message }}
This repository has been archived by the owner on Nov 5, 2024. It is now read-only.
I understand that the maintainers of aws-sdk-go-v2 (this repo) don't want to own the burden of supporting DAX. However, this looks like an organizational problem; please don't put the burden on customers.
Why does this SDK not support DAX? Why is DAX a second-class citizen? It's a service offered by AWS, is it not? And this is the AWS SDK, is it not? Then it should support it.
Code Comparison
No response
Observed Differences/Errors
n/a
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Thank you for bringing this up. The DAX SDK's compatibility with newer SDK versions has indeed been a recurring topic. Initially, we discussed this in this thread.
To clarify, the Go SDK never had support for DAX. Instead, it's supported through a separate client maintained by the DynamoDB service team, which integrates with the various AWS SDKs. The repository you've mentioned, aws-dax-go, are not under the direct purview of the AWS SDK team.
AWS SDKs are largely code-generated from the API models of the various AWS services. Since DAX is an abstraction over DynamoDB and not a standalone service, it will not be available through the AWS SDK.
Acknowledging your concerns, it's clear there's significant demand for DAX support across SDKs. While our team has previously escalated this need to the DynamoDB team for them to extend support to newer SDK versions, we were turned down.
I'm going to collect all the feedback we got across the various SDKs and upstream this once again to the Dynamodb team in hopes that they will prioritize this and continue support for the newer SDK major versions.
I have reached out to the DAX team, they have confirmed that they do have plans for supporting newer SDK versions, but I'm not able to share an ETA.
If you have any additional questions / concerns please reach out to the DAX team directly either by opening new issues on their github repo, or by creating an internal support ticket via the AWS developer console.
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Pre-Migration Checklist
Go Version Used
Go 1.22
Describe the Migration Issue
My team can't upgrade to v2 unless the DAX SDK (https://github.com/aws/aws-dax-go) upgrades to v2 too.
However, that repository looks abandoned:
dynamodbiface.DynamoDBAPI
functions aws-dax-go#52and PRs don't get attention: aws/aws-dax-go#43
See also
I understand that the maintainers of
aws-sdk-go-v2
(this repo) don't want to own the burden of supporting DAX. However, this looks like an organizational problem; please don't put the burden on customers.Why does this SDK not support DAX? Why is DAX a second-class citizen? It's a service offered by AWS, is it not? And this is the AWS SDK, is it not? Then it should support it.
Code Comparison
No response
Observed Differences/Errors
n/a
Additional Context
No response
The text was updated successfully, but these errors were encountered: