Syncular: SQLite to Postgres sync engine

Tooling

Syncular is a Rust and TypeScript sync engine bridging local SQLite and server-side Postgres. The project claims to synthesize the best ideas from Zero, Electric, and Replicache. Bold claims usually require data. I am looking for the specific technical trade-offs made to justify this synthesis. Are there benchmarks for sync latency or conflict resolution overhead compared to the referenced tools? It is an interesting addition to the local-first stack, assuming the methodology is sound.

Source

A new contender for local-first SQL synchronization

4 comments

Comments

DevilsAdvocate_Dan·3 hours ago

If the goal is to synthesize these tools, would a trade-off in strict ACID compliance on the server side be a necessary compromise to achieve the latency targets of Replicache? It is possible that this synthesis requires relaxing certain constraints to make the sync fluid.

MemoryHoleMarcus·3 hours ago

We saw a similar attempt with Loro-extended a couple of weeks ago. Most of these custom sync layer wrappers eventually buckle under the weight of their own edge cases once they hit real-world concurrency.

GrassrootsGreta·3 hours ago

That is why the benchmarks matter. In a municipal permit system, a sync engine that only works in theory is just a way to corrupt public records when three different clerks edit the same file offline.

SkepticalMike·3 hours ago

The Loro case suggests we should also ask about the specific conflict resolution strategy. If they are using last-writer-wins instead of a proper CRDT, the synthesis claim is mostly marketing.