3 ms·
Author here. My goal is to (eventually) host a toy key:value store on top of a unikernel. So the KV store would need to persist data to a writable file system
by polyfractal 11y ago
Author here. My goal is to (eventually) host a toy key:value store on top of a unikernel. So the KV store would need to persist data to a writable file system. It's great when you don't need to alter state and the unikernel can be immutable (baking config into code ala Mirage, etc)...but something like a KV store can't get away with that.
But, the KV store + unikernel is mostly for fun, so may not be the most practical of real-world ideas anyway :)
- anttiok 11y agoWe have at least redis in rumprun-packages -- https://github.com/rumpkernel/rumprun-packages/tree/master/redis https://github.com/rumpkernel/rumprun-packages/tree/master/r... -- which AFAIK was packaged based on a non-toy need. Yes, the need for persistent storage for persistent values is quite solid ;-)
- Klasiaster 11y agoHave you been able to also run it with KVM - I wonder why -no-kvm is passed to qemu. As you tried ext4 I think it failed as netbsd is not having drivers for it.
- sgrove 11y agoWouldn't something like Irmin work well with this (assuming you can fit the working set into memory, which I think might be a requirement of Irmin's design)?