News for hackers. Stuff that matters.
Re:Sync Engines Are the Future by mentalgear on Friday March 21, 2025 @08:02AM (#43434621)
if you know of other honourable mentions, reply with their source link!
Re:Sync Engines Are the Future by mentalgear on Friday March 21, 2025 @09:45AM (#43435631)
Convex I didnt know yet - looks really crisp (even has svelte support) ! Do you have experience with it? Does it support (decentralized) E2E?
Re:Sync Engines Are the Future by aboodman on Friday March 21, 2025 @02:47PM (#43439535)
No, Convex is a client/server system like zero, electric, instant, powersync.

If you want a fully decentralized system, check out jazz. It is the best of these currently IMO.

Re:Sync Engines Are the Future by mentalgear on Wednesday March 26, 2025 @04:58AM (#43480174)
Yeah, my question was more about E2E, optionally decentralised.

Did you use Convex, what's your general experience?

Re:Sync Engines Are the Future by sergioisidoro on Friday March 21, 2025 @11:00AM (#43436513)
I've been very curious about electric -- the idea of giving your application a replicated subset of your databse, using your api as a proxy, is quite interesting for apps where the business layer between the db and the client is thin (our case).

edit: Also their decision to make it just one way sync makes a LOT of sense. Write access brings a lot of scary cases, so by making it only read sync eases some of my anxieties. I can still use Rest / RPC for updating the data

Re:Sync Engines Are the Future by bushido on Friday March 21, 2025 @10:42AM (#43436297)
https://rxdb.info/ is a good one.
Re:Sync Engines Are the Future by hop_n_bop on Friday March 21, 2025 @07:18PM (#43441736)
more the basis for building your own backend sync-solution in Go than a complete product, this library does an rsync-like protocol to minimize data transferred to sync up two filesystems; its very general building block:

https://github.com/glycerine/jcp