Comment by TeeWEE
2 years ago
Congrats.
How does this deal with schema changes? We have a solution where old clients can store objects that have new fields unknown to the client. Then when the clients updates the data is visible.
Do you have client libraries for mobile? Swift & Kotlin?
Does it support partial sync and fetch when you need an “archived” item? In my experience you only want the “working set” of data on the client. Not everything.
Cool work! CRDTs are the solution to this.
It works similarly: migrations flow as part of the replication stream and clients apply them immediately, so that new data fits the local schema. New columns and etc might not immediately be exposed to the client app, but everything will works for old clients.
You can learn more about our support for migrations here: https://electric-sql.com/docs/usage/data-modelling/migration...
Native clients will be coming a bit later.
You can use the shapes to control what data syncs to the device: https://electric-sql.com/docs/usage/data-access/shapes
I was also going to ask about mobile clients, then saw your comment.