Did I just break their conflict-free sync?
Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps
151–160 of 173 posts
Re: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps
#152The docs indicate[1] that electric's syncing logic, "shapes", are handled transactionally. How would electric handle an initial sync of 500mb or an initial sync of 10gb? [1]: https://electric-sql.com/docs/usage/data-access/shapes#data-loading
Apps with large dataset have their own characteristics: they are more tolerant to slower initial sync. We can resume replication at point-in-time, so even if a shape takes long to load, we can resume replication at the point we started synching the shape.
We will be working on the engineering to handle transferring large shapes.
Re: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps
#153Would this work as a tool to sync a central server's parts of your postgres data to your distributed webapp backends local-copy, as opposed to all the way to user front-end. i.e. nodejs instead of the browser. Or is there a better tool for that?
yes, ElectricSQL works for webapps with nodejs: https://electric-sql.com/docs/integrations/drivers/server/no...
Re: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps
#154Did I just break their conflict-free sync? https://i.imgur.com/MiEWHA9.png
Thank you for playing with our demos and finding this issue!
We'd welcome very much if you could reproduce the steps and report an issue: GH: https://github.com/electric-sql/electric/issues Discord: https://discord.com/channels/933657521581858818/107968886985...
Re: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps
#155Re: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps
#156Earlier quoted context omitted.
This is the fifth comment I’ve counted plugging Powersync in this thread. I guess it’s the nature of the startup hustle game but this level of promotion in someone else’s Show HN thread feels a little distasteful. Maybe you could post your own Show HN?
I hear you, thanks for sharing your thoughts and for the suggestion. Noted. I didn’t mean to just plug — I thought I was contributing to the discussion and that some people may find another implementation relevant/interesting.
Since you are here, I would love to understand what are the conceptual and architectural differences between ElectricSQL and PowerSync.
Re: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps
#157Congrats. How does this deal with schema changes? We have a solution where old clients can store objects that have new fields unknown to the client. Then when the clients updates the data is visible. Do you have client libraries for mobile? Swift & Kotlin? Does it support partial sync and fetch when you need an “archived” item? In my experience you only want the “working set” of data on the client. Not everything. Co…
I was also going to ask about mobile clients, then saw your comment.
Re: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps
#158When `brew install postgresql` is too hard.
postgresql has conflict-free multi-master sync now? That's incredible work, can't believe I missed it!
https://www.researchgate.net/publication/359578461_Continuou... has entered the chat
Re: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps
#159Earlier quoted context omitted.
What does the local client side look like? Could it be wrapped in a node daemon to sync to a local SQLite file?
Hey, one of the devs here! JS library already works with Node via `better-sqlite3` library. We provide a way to set up listeners to data changes, or you can just start up a node client and do some work periodically on the synced data.
Ah that's fantastic.