Electric-sql for file-first approach

[ctwhome]

hi! I am building a note-taking application with an emphasis on a file-first approach, meaning that the application (web with electron) will make changes in the file, and those need to be real-time in sync with all collaborators and user other devices (mobile, tablet).

Would it be possible to have such a system with electric-sql? the app also needs to handle media files like videos, images, and audio, all of them stored in the computer file system of the user, and somehow syncing everywhere?

[balegas]

ElectricSQL is best fit for synchronizing relational data. We've used Electric to store small data files in-database, but for large media files is best to use an external storage.
It's possible to use ElectricSQL alongside a storage service and associate URLs and their respective data.

[ctwhome]

The idea is that all data files and media are stored in the hard disk of the user, then synced everywhere, an approach of how Obsidian.md does, although they do not share their stack for the synchronization part. I guess the whole thing should behave like Google Drive, always listening for file changes, but also keeping indexes in a database-like to perform searches. Could that be possible Electric-sql then?

[KyleAMathews]

You could store a hash of files in the db and upload changes to e.g. s3 and then clients download new files as they see them.

You should also checkout electric's experiments with yjs as you could use yjs to sync changes to text files.

[ctwhome]

Thanks for the answers, i think it is worth the try to have the ultimate offline mode, file ownership, with realtime sync between active participants... it sounds like a holy grail to me.