> How similar is this to MeteorJs minimongo collections? > Does this provide an architecture where a client subscribes to a collection and the server keeps tra

> 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.