💥 Replace BoltDB Storage to Gorm SQL #237
Merged
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.
The current implementation using BoltDB has significant performance issues as the
Message
table grows. The problem lies in the lack of indexing for theID
andTicker
fields, resulting in lengthy loading times and backpressure on the web server.This pull request completely revamps the storage system using Gorm and introduces an SQL database (SQLite, MySQL, PostgreSQL). By implementing improved indexing, the overall performance is expected to greatly improve. Additionally, this update enables separating the API from the underlying storage (database).
Please note that this pull request introduces a significant breaking change for the ticker.