Implement search indexes for mongo collections#18
Merged
Conversation
This file contains hidden or 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
1 participant
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 PR introduces the creation and organization of MongoDB indexes across the application collections to improve query performance and optimize the main read paths of the system.
Both simple and compound indexes were defined based on the most common access patterns, ensuring efficient filtering, especially in scenarios involving RealmId and key identifier fields such as Username, Name, UserId, and ClientId.
In addition, the index creation is centralized during application startup, ensuring that the database is properly prepared when the service boots, without requiring any manual intervention.
This improvement helps reduce query latency and enhances the system’s scalability as data volume grows.