Add secondary indexing via partiton key support #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a breaking change.
Secondary indexing can be achieved in a few ways in DynamoDB - GSIs/LSIs are the most common way of achieving this.
An efficient way to use table capacity is to use single table design patterns and write data in different formats depending on the read use cases (For example: https://aws.amazon.com/blogs/compute/creating-a-single-table-design-with-amazon-dynamodb/)
Following a pattern I have used previously, I've added support for adding secondary indexes via another ID, which is then supported via a separate query method to make it more transparent to the end user.