Live data from Hacker News

Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps

electric-sql.com

171–173 of 173 posts

Re: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps

#171
post #169
post #156

Earlier quoted context omitted.

Since you are here, I would love to understand what are the conceptual and architectural differences between ElectricSQL and PowerSync.

ElectricSQL stores additional data in the source PostgreSQL database, while PowerSync stores this in a separate data store in its sync service. Because of this, ElectricSQL requires schema changes and has some schema restrictions on the source database. ElectricSQL uses CRDTs for merging changes, via the Electric backend. PowerSync records changes per transaction on the client and lets the developer write changes to…

Both these assumptions are incorrect.

We maintain consistency and integrity across shape boundaries.

Re: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps

#172
post #169

Earlier quoted context omitted.

ElectricSQL stores additional data in the source PostgreSQL database, while PowerSync stores this in a separate data store in its sync service. Because of this, ElectricSQL requires schema changes and has some schema restrictions on the source database. ElectricSQL uses CRDTs for merging changes, via the Electric backend. PowerSync records changes per transaction on the client and lets the developer write changes to…

Both these assumptions are incorrect. We maintain consistency and integrity across shape boundaries.

Thanks for the clarification
Post reply on HN