Introduce datastore v2 #64
                
     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.
  
    
  
    
Motivation
Our current usage of BadgerDB has proven to be too resource-intensive, consuming unacceptable amounts of memory and CPU in our specific use case (>10GiB in common).
Design
To mitigate this, we have refactored our datastore to directly write records into files. After reaching a certain limit of records, we switch to a new file for continued writing. Additionally, we now compress previous data files to reduce spaces.