Comment by thruflo
2 years ago
Hey,
This is the exact pattern we target :)
Drop Electric onto an existing Postgres data model and use the Shape-based sync to manage dynamic partial replication of subsets of data between central Postgres and local SQLites: https://electric-sql.com/docs/usage/data-access/shapes
James
Congrats on the launch. I’ve been keeping an eye on these sorts of tools for a while and had a look at this after it was mentioned on HN the other day. Looks great.
We currently use Hasura subscriptions to pull data to the frontend (effectively select * from table where account_id = X and updated > recently). We then funnel changed rows into mobx objects so we have a lovely object graph to work with.
I’m imagining doing the same with electric so I guess you’d use notify to hear that there has been a change, then figure out if it’s in a table you care about and then select the updated records from that to merge into mobx?
Basing that off what I see in here: https://github.com/electric-sql/electric/blob/main/clients/t...
Interesting, I don’t know enough about MobX to be sure but yes, you can use the notifier to subscribe to data change notifications and query to get the changed rows.
We’d definitely be interested in chatting through the reactivity model you use if you’d be up for it.
This is awesome. I love the pattern, and the way you’ve built for this as a first-class concern is great.