Conversation

Arguably things are even worse than discussed in that article. Take Firebase, for instance: it implements offline caching, but that's very different from sync. You have to design a whole replication strategy on top to get something like "a synced file format."

Web Native File System Technical Design Overview – Fission

CouchDB seems like the closest solution, if you can design a conflict-free model. But I spent the last week getting into the details of actually operating a multi-user service, and I am now quite thoroughly spooked!

try

Both new to me, thanks—will read up.

thanks

. Founder of

here Andy 👋 We designed a file system on top of IPFS, this is a presentation that goes into detail blog.fission.codes/web-native-fil We’re participating with the

@DecentralizedID

to work on personal data store standards

fission.codes

Brooklyn and Daniel from the Fission team present a technical overview of the Web Native File System.

Replying to

Thanks! I'm very excited about the distributed design direction. Unfortunately a file system doesn't quite fit my application model: I'd still need to build a database on top of this for querying/indexing. I see there's a TODO for databases in the white paper?

6:48 PM · May 15, 2021TweetDeck

Replying to

and

yep. Happy to connect you with

@expede

if you want to help define what you need / what you want to see out of a distributed database. We’re committed to building it.

I'm glad you all are working on that! Alas this project already has a lot of risks, so I'll be looking for a more "boring" solution at the data layer.

Show replies

Brooklyn Zelenka

Replying to

Hey 👋 yes, the idea is to build a CRDT-backed, local first distributed database that works well in browsers, on top of our file system. It’s not built yet. Totally understand that you’re looking to derisk! I’d still love to pick your brain on requirements if you have time 🙏