chiselstore
chiselstore copied to clipboard
chiselstrike
SQLite + Little Raft = 🚀
With relaxed reads, there's currently no guarantee on read-your-write consistency. This is because a write will be acknowledged when the write is applied to the state machine of the _leader_,...
Suggested by Andy Pavlo: turn on SQLite strict mode to avoid some idiosyncrasies.
Currently `gouged` assumes that all nodes are running on local machine and uses a mapping between nodes and ports. Make the peer IP addresses configurable to make testing with multiple...
The connection pool currently grows without bounds. Let's enforce some limit to it.
My impression is that gouged is the service that provides the SQLite abstraction? If this is correct, is there any interest in writing a very simple python client to this...
We don't need to replicate SQL read commands to other nodes if they don't have side-effects.
We currently use file-backed SQLite databases because the basic in-memory SQLite does not seem to support concurrent reads: https://github.com/chiselstrike/chiselstore/commit/75ec0c75950499a91ef5dffcdc368cdc67924e38 Let's look at ways to turn on in-memory again. For example,...
Currently, the replicated Raft log grows unbounded. First, we need to add Raft snapshot support to Little Raft, which allows truncating the log. We then need to add snapshot support...