4 ms·
if you know of other honourable mentions, reply with their source link!
by mentalgear 2y ago
if you know of other honourable mentions, reply with their source link!
- aboodman 2y agoThere are so many: - https://github.com/electric-sql/electric https://github.com/electric-sql/electric - https://github.com/powersync-ja https://github.com/powersync-ja - https://github.com/get-convex https://github.com/get-convex - https://github.com/tinyplex/tinybase https://github.com/tinyplex/tinybase - https://github.com/garden-co/jazz https://github.com/garden-co/jazz
- mentalgear 2y agoConvex I didnt know yet - looks really crisp (even has svelte support) ! Do you have experience with it? Does it support (decentralized) E2E?
- aboodman 2y agoNo, 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.
- mentalgear 2y agoYeah, my question was more about E2E, optionally decentralised. Did you use Convex, what's your general experience?
- sergioisidoro 2y agoI'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
- bushido 2y agohttps://rxdb.info/ https://rxdb.info/ is a good one.
- hop_n_bop 2y agomore 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 https://github.com/glycerine/jcp