JuiceFS on CloudFlare workers so I can map the FS calls to S3 / CF Durable Objects

[gedw99]

I know how to run golang on Cloudflare workers, Its just a matter of remapping the calls to the underlying HTTP request.

SO I was thinking that maybe we can map the FS calls too using JuiceFS, so then we can use S3 or even the CF Durable Objects.

[zhijian-pro]

I did not understand this question, could you please explain it in detail?

[vicaya]

CF worker is just a v8 (javascript) runtime, so FUSE wouldn't work. juicefs enterprise already has a python SDK that can be used without FUSE. People want the js (and maybe other languages) equivalent.

To be future proof, we should target wasi (https://github.com/WebAssembly/wasi-filesystem), so that any languages with wasm target can take advantage of juicefs in wasm runtimes, which is arguably the future of serverless runtimes.

[gedw99]

WASM targeting would be nice …

I already run a ton of stuff in WASM with wazero . It’s very easy to control the FS capability mapping to control what part of the FS the WASM can interact with.

https://github.com/syumai/workers allows golang compiled to WASM to run on Cloudflare .

i Las run the same WASM ( with a different golang build tag ) to target bare metal , as well as Browsers.

If I could use these with juiceFS is would be fabulous. Because then I can map the FS to S3 be fully serverless .

I also run the WASM locally on desktops and mobile this way and map to the real FS without S3 too

[zhijian-pro]

Our community version will release a Python SDK in v1.3, subsequent releases may include go SDK, the release time is not yet determined.

[vicaya]

It'd be great to implement the nfsv4 protocol in the juicefs client daemon (pure go nfsv4 server library: https://github.com/smallfz/libnfs-go), so client libs are basically covered by https://github.com/sahlberg/libnfs and friends (including python, go, rust etc.) and all the kernel nfs clients.