sqlite

Ah, yes! Thank you for clarifying. (sorry for the late reply) This actually works out of the box, sorry if if this wasn't clear. When you run a gun server ( `npm start` or see https://github.com/gundb/gun-starter-app ), it by default saves persists data to disk. This way the gun server acts as a storage node, ready to provide the data to clients. The default options are, and extensions for: - Dump JSON to disk. - Backup to S3. - Level adapter https://github.com/PsychoLlama/gun-level - SQLite adapter https://github.com/gundb/sqlite Note, that the Level adapter is also compatible with many other storage engines. Is this what you were looking for?

Dangit, I trust the CoreOS team more/better than a lot of people in the space. Torus would have been so useful. At the other end of the spectrum though, maybe this is reasonable? As a developer, my first thoughts for "I want my own S3" is not etcd (strong consistency) but projects like https://github.com/minio/minio , or even using eventually consistent SQLite replication / synchronization tools https://github.com/gundb/sqlite . So that makes me ask about rook.io too, what layer of the "stack" is it trying to fit into? Obviously pretty low, but that also seems unnecessary (and part of why I suspect Torus is stopping).