cat picture button blog post #4
Draft
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 post aims to build the reader's intuition around what happens when an OLTP database takes on a high volume of write operations while also trying to perform aggregation queries over the inserted data.
Indexing data can help temporarily, but if the table continues to grow, writes will slow down, increased database size, and the operational overhead of maintaining indexes for every column needing to be queried can introduce unwanted complexity.
OLTP databases are designed for querying a lot of data and in complex ways as to provide meaningful insights into the valuable data that you have collected.
This post should introduce scratchdata as a solution that Alex could use to solve their data problem.