So if it needs to work offline, but it syncs with a server, then you use both? (And the schema becomes some kind of lowest common denominator?)
replyI would probably do an event-source architecture, where you record events on the client and then push them to the server when you're reconnected. It has a lot of benefits, for instance, trivial auditing and free serialization.
replyyeah essentially, see electricsql
replythough they also have "pglite" running in wasm.
same concept though, sync slices to an embedded db.
SQLite is embedded for local applications with one writer mostly.
replyIn 2026 that advice feels antiquated. SQLite now is absolutely useful now for concurrent, mutli-writer applications.