Show HN: Bi-directional sync between Postgres and SQLite
39 by matharmin | 4 comments on Hacker News.
Hi HN, Today we’re launching PowerSync, a Postgres<>SQLite bi-directional sync engine that enables an offline-first app architecture. It currently supports Flutter, React Native and web (JavaScript) using Wasm SQLite in the browser, with more client SDKs on the way. Conrad and I (Ralf) have been working on our sync engine since 2009, originally as part of a full-stack app platform. That version of the system is still used in production worldwide and we’ve learnt a lot from its use cases and scaling. About a year ago we started on spinning off PowerSync as a standalone product that is designed to be stack-agnostic. If you’d like to see a simple demo, check out the pebbles widget on the landing page here: https://ift.tt/hiJ43YF We wrote about our architecture and design philosophy here: https://ift.tt/ekOHWba... This covers amongst other things how we designed the system for scalable dynamic partial replication, why we use a server authority architecture based on an event log instead of CRDTs for merging changes, and the approach to consistency. Our docs can be found here: https://ift.tt/58RZckK We would love to hear your feedback! - Ralf, Conrad, Kobie, Phillip and team
39 by matharmin | 4 comments on Hacker News.
Hi HN, Today we’re launching PowerSync, a Postgres<>SQLite bi-directional sync engine that enables an offline-first app architecture. It currently supports Flutter, React Native and web (JavaScript) using Wasm SQLite in the browser, with more client SDKs on the way. Conrad and I (Ralf) have been working on our sync engine since 2009, originally as part of a full-stack app platform. That version of the system is still used in production worldwide and we’ve learnt a lot from its use cases and scaling. About a year ago we started on spinning off PowerSync as a standalone product that is designed to be stack-agnostic. If you’d like to see a simple demo, check out the pebbles widget on the landing page here: https://ift.tt/hiJ43YF We wrote about our architecture and design philosophy here: https://ift.tt/ekOHWba... This covers amongst other things how we designed the system for scalable dynamic partial replication, why we use a server authority architecture based on an event log instead of CRDTs for merging changes, and the approach to consistency. Our docs can be found here: https://ift.tt/58RZckK We would love to hear your feedback! - Ralf, Conrad, Kobie, Phillip and team