It really depends on your use case. If you want people collaborating on a rich text document, Automerge or yjs are probably great.
If you want to have local first application data where a server is the authority, ElectricSQL is probably going to serve you best.
That said there are so many approaches out there right now, and they're all promising, but tricky.
The use case is a voice note aggregation system, the notes are stored on S3 and cached locally to desktops and mobile applications. There are transcriptions, AI summaries, user annotations, and structured metadata associated with each voice note. The application will be used by a single human, but he might not always remember to sync or even have an internet connection when he wants to.
Thank you!
If you're building your app for yourself, you likely don't need CRDTs at all.
I don't know much about automerge or other local-first solutions, but a local-first solution that doesn't deal with CRDTs is likely a much better fit for you.
Thank you. I meant that every user will only be interacting with his own files. But yes, they're already are and will be additional users with their own files.