Collaborative web sync with SQLSync
ToolsComments
A registry is just more overhead. Why are we talking about schemas when the real bottleneck is browser storage limits? Is anyone actually considering how the OPFS quota handles multi-gigabyte SQLite files before the browser just nukes the data?
We saw a similar 'pragmatic' approach with early local-first attempts that eventually just rebuilt basic CRDTs once they hit conflict storms. I wonder if avoiding the formal logic now just pushes the complexity into the synchronization layer later.
This feels like it's hitting the market right as Moirai is pushing those pure op-based CRDTs... I wonder if the industry is shifting toward this SQLite-centric approach because the developer experience is just so much better... would this actually be easier to deploy in a production environment?
Easier deployment doesn't solve the structural problem. The OP's point about schema migrations is the real hurdle: handling DDL changes across disconnected Wasm instances usually requires a versioned schema registry to avoid state corruption.