Earlier quoted context omitted.
Can I have a tshirt?
Yes!
:)
Show HN: Bi-directional sync between Postgres and SQLite
81–90 of 107 posts
Re: Show HN: Bi-directional sync between Postgres and SQLite
#82This seems really interesting and I do have some questions:
How similar is this to MeteorJs minimongo collections?
Does this provide an architecture where a client subscribes to a collection and the server keeps track of which data the client has and only sends minimal update messages?
Is this ideal for intense real-time applications (ex:Chat)?
Is self-hosted a future option?
Re: Show HN: Bi-directional sync between Postgres and SQLite
#83Looks a lot like a light version of ElectricSQL (https://github.com/electric-sql/electric). Why should I use PowerSync instead?
Re: Show HN: Bi-directional sync between Postgres and SQLite
#84Looks a lot like a light version of ElectricSQL ( https://github.com/electric-sql/electric ). Why should I use PowerSync instead?
A detailed comparison can be found here: https://www.powersync.com/blog/electricsql-vs-powersync
Re: Show HN: Bi-directional sync between Postgres and SQLite
#85This seems really interesting and I do have some questions: How similar is this to MeteorJs minimongo collections? Does this provide an architecture where a client subscribes to a collection and the server keeps track of which data the client has and only sends minimal update messages? Is this ideal for intense real-time applications (ex:Chat)? Is self-hosted a future option?
> How similar is this to MeteorJs minimongo collections?
> Does this provide an architecture where a client subscribes to a collection and the server keeps track of which data the client has and only sends minimal update messages?
It is similar in that PowerSync also supports local queries and real-time/streaming updates. However, I believe minimongo / MeteorJS uses an in-memory database, while PowerSync fully persists the data, allowing full offline capabilities.
The PowerSync client does subscribe to incremental changes, similar to MeteorJS (although the client keeps track of the state, not the server).
> Is this ideal for intense real-time applications (ex:Chat)?
Yes, PowerSync will work well for that. One caveat is that PowerSync may have slightly more latency than some other real-time systems (in the order of tens to hundreds of milliseconds), in favor of consistency and offline persistence of data. This means PowerSync will not be suitable for time-sensitive games as an example.
> Is self-hosted a future option?
Yes - see other comments for details on self-hosting and our open-source plans.
Re: Show HN: Bi-directional sync between Postgres and SQLite
#86Looks a lot like a light version of ElectricSQL ( https://github.com/electric-sql/electric ). Why should I use PowerSync instead?
A detailed comparison can be found here: https://www.powersync.com/blog/electricsql-vs-powersync
Hi! I'm not familiar with either engine, but I'm confused with the text in the comparison (see below). Couldn't ElectricSQL be used within the backend to enforce policies or am I missing something?
> Writes are made directly to your Postgres database via the Electric sync service (bypassing your backend application),
Re: Show HN: Bi-directional sync between Postgres and SQLite
#87Let me throw SymmetricDS into the ring: https://symmetricds.org/
In my opinion it is quite underestimated giving its various cross platform and cross product sync capabilities. My first experiences with it are quite promising.
Re: Show HN: Bi-directional sync between Postgres and SQLite
#88Earlier quoted context omitted.
A detailed comparison can be found here: https://www.powersync.com/blog/electricsql-vs-powersync
Hi! I'm not familiar with either engine, but I'm confused with the text in the comparison (see below). Couldn't ElectricSQL be used within the backend to enforce policies or am I missing something? > Writes are made directly to your Postgres database via the Electric sync service (bypassing your backend application),
ElectricSQL's architecture is documented here:
https://electric-sql.com/docs/reference/architecture#primary...
https://electric-sql.com/docs/reference/architecture#data-fl...
The docs explain how the Electric sync service publishes a logical replication stream that the Postgres database subscribes to. The Electric sync service is responsible for validating permissions based on the DDLX configuration.
Re: Show HN: Bi-directional sync between Postgres and SQLite
#89Earlier quoted context omitted.
Hi! I'm not familiar with either engine, but I'm confused with the text in the comparison (see below). Couldn't ElectricSQL be used within the backend to enforce policies or am I missing something? > Writes are made directly to your Postgres database via the Electric sync service (bypassing your backend application),
ElectricSQL's architecture is documented here: https://electric-sql.com/docs/reference/architecture#primary... https://electric-sql.com/docs/reference/architecture#data-fl... The docs explain how the Electric sync service publishes a logical replication stream that the Postgres database subscribes to. The Electric sync service is responsible for validating permissions based on the DDLX configuration.
Yup, this is correct.
We have had some requests / discussions around adding hooks to the sync service that will support custom logic on the write path (as per https://github.com/electric-sql/electric/discussions/565). This seems like a good idea but they don't exist yet.
Re: Show HN: Bi-directional sync between Postgres and SQLite
#90Let me throw SymmetricDS into the ring: https://symmetricds.org/ In my opinion it is quite underestimated giving its various cross platform and cross product sync capabilities. My first experiences with it are quite promising.
Thanks for the link, I haven't come across SymmetricDS before. The list of supported databases is impressive.
It appears to be primarily aimed at server-to-server replication. It does support Android and iOS, but I don't see much documentation on that. Do you know if it works in practice to implement offline-first applications?