forked from docker/libkv
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filesystem backend #49
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
while ago i've started implementing a local backend driver for libkv using the filesystem. I'm doing this mostly to learn the insides of the codebase (aka for fun) but also some interesting concepts have emerged.
First. What's wrong with boltdb backend?
With an FS backend you can utilize inotify to implement watching and you can have plain files as "values". If are accessing your etcd, zk, et. using libkv having a backend like this you can have versioned test/mock data for development and testing. Or, for example, speed development by having direct access to your "DB".
Some issues.
How does this concept sound to you? Will it be useful?
Cheers
The text was updated successfully, but these errors were encountered: