I've been very curious about electric -- the idea of giving your application a replicated subset of your databse, using your api as a proxy, is quite interesting for apps where the business layer between the db and the client is thin (our case).
edit: Also their decision to make it just one way sync makes a LOT of sense. Write access brings a lot of scary cases, so by making it only read sync eases some of my anxieties. I can still use Rest / RPC for updating the data
more the basis for building your own
backend sync-solution in Go than a complete
product, this library does an rsync-like
protocol to minimize data transferred to sync
up two filesystems; its very general building block:
- Zero Sync: https://github.com/rocicorp/mono
- Triplit: https://github.com/aspen-cloud/triplit