Luke Frisken

> Can you elaborate on this, and specifically describe what we need to add to this document: https://docs.google.com/document/d/1Vyg2J60zRU6023KXBjZx8CP3V-Nz6hPOUCMplbCxVB4/edit?usp=sharing @apruden2008 I've referenced that document in this document. I see that document...

It would be nice to get this merged at some point or relocated to somewhere more visible

Libraries that look interesting could perhaps be used or inspiration for solving this: + https://github.com/lostatc/acid-store + https://github.com/zboxfs/zbox + https://github.com/facebook/rocksdb/wiki/Transactions + https://www.sqlite.org/lang_transaction.html Switching to Sqlite or RocksDB for storage has been...

I'm guessing maybe not, but if the aggregation fails for some reason (are we expecting it could fail or does verification catch all possible issues?) then their contribution will not...

> would you mind communicating the change you are making and what problem does it solve? @ibaryshnikov valid concerns. A few reasons: 1. Continuation of the changes made in #288...

If we can write code that behaves more predictably, and explicitly (less hidden side effects), then hopefully we can reduce the amount of debugging required in the first place.

For some more context about these changes, I'm currently working on #365 which has some failing unit tests. As part of diagnosing/fixing this I would like to write some more...

@ibaryshnikov the cause of which problem specifically? This pull request not claiming to help address anything more than the issues that have been referenced. Are you're worried that the changes...

@ibaryshnikov I'm guessing we probably had the similar discussion on slack, but for the sake of others reviewing/reading, I'll reply here too. This is a quality of life refactor, only...

From the conversation in the meeting today, I should mention that this PR is not intended to introduce a universal way to interact with the storage layer, but more is...