Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
I've added the DynamoDB kv-store and followed the same naming methods as NATS and Badger to stay consistent (Like Set, Get, and Delete operations). The code also largely follows the implementation details of NATS and Badger also for consistentcy and coherency. The only difference is that DynamoDB supports multiple attributes for keys so I made it accept a map of any values rather than just setting and getting strings.
I also ran my own integration tests against it using a local dynamodb container and even tested it against my own AWS account dynamodb. It worked as expected but I didn't commit the integration test file here because both NATS and Badger didn't have any specific implementation testing details. If needed, I can add the integration test file and the steps i took to test it.
Aside from that, all the requirements were met: