Hello, I’ve thrown together a proof of concept filesystem layer in C++, using FUSE’s low-level async API.
It seems to handle standard file operations correctly: git is able to operate on top of it. But, it doesn’t do proper permissions checking, and there’s no shortage of TODOs in the code for spots where error handling isn’t fleshed out. It isn’t ready for prime time. As such, I hope nobody will run off and post this around the Internet as “filesystem layer for foundationdb!”
I’m hoping it will spark some discussion on how such a layer ought to be interact with/store data in FDB. My rough outline for what I’m doing (to the extent that I finished implementing it) is in
(On a non-FDB front, this is my first real use of modern C++. I last spent any time with it circa 1999. I’d be very interested in hearing, perhaps via outside of the forum, opinions on the use/abuse of C++ in my code.)