Hi everyone,  
I’ve been working on a project called Loomabase, an offline-first synchronization engine written in Rust.  
The goal is to make it easier to build applications that continue working when devices go offline and automatically synchronize changes once connectivity is restored.  
Loomabase uses SQLite on clients and PostgreSQL on the server, with conflict resolution handled through column-level CRDTs and Lamport clocks. Instead of treating an entire row as a single unit, concurrent updates can be merged at the field level when possible.  
Current features include:  
SQLite ↔ PostgreSQL synchronization  
Column-level Last-Writer-Wins CRDTs  
Deterministic conflict resolution using Lamport clocks  
Partial replicas and selective synchronization  
Multi-tenant support  
Schema fingerprinting for compatibility checks  
Transport-agnostic sync protocol  
The project is still in an early pre-1.0 stage, but the core architecture is taking shape and I’d love to get feedback from people who have experience with distributed systems, databases, synchronization engines, or offline-first applications.  
Some questions I’m particularly interested in:  
Are there obvious flaws in the CRDT approach?  
What are the biggest challenges around schema evolution?  
Does the partial replication model make sense?  
What scalability issues would you expect to appear first?  
Are there existing systems that solve these problems better?

Any feedback, criticism, or suggestions would be greatly appreciated.

I built an offline-first sync engine for SQLite ↔ PostgreSQL using column-level CRDTs