Skip to main content

New best story on Hacker News: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps

Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps
425 by samwillis | 121 comments on Hacker News.
Hi HN, James, Valter, Sam and the team from ElectricSQL here. We're really excited to be sharing ElectricSQL with you today. It's an open source, local-first sync layer that can be used to build reactive, realtime, offline-capable apps directly on Postgres with two way active-active sync to SQLite (including with WASM in the browser). Electric comprises a sync layer (built with Elixir) placed in front of your Postgres database and a type safe client that allows you to bidirectionally sync data from your Postgres to local SQLite databases. This sync is CRDT-based, resilient to conflicting edits from multiple nodes at the same time, and works after being offline for extended periods. Some good links to get started: - website: https://ift.tt/zp9EHt0 - docs: https://ift.tt/gq5aCtI - code: https://ift.tt/DOiq18W - introducing post: https://ift.tt/WjR68sK... You can also see some demo applications: - Linear clone: https://ift.tt/m296aYq - Realtime demo: https://ift.tt/OlDnwTk - Conflict-free offline: https://ift.tt/sgZq3aR The Electric team actually includes two of the inventors of CRDTs, Marc Shapiro and Nuno Preguiça, and a number of their collaborators who've pioneered a lot of tech underpinning local-first software. We are privileged to be building on their research and delighted to be surfacing so much work in a product you can now try out.

Comments

Popular posts from this blog

New best story on Hacker News: Ask HN: I’m an FCC Commissioner proposing regulation of IoT security updates

Ask HN: I’m an FCC Commissioner proposing regulation of IoT security updates 449 by SimingtonFCC | 144 comments on Hacker News. Hi everyone, I’m FCC Commissioner Nathan Simington, and I’m here to discuss security updates for IoT devices and how you can make a difference by filing comments with the FCC. As you know, serious vulnerabilities are common in IoT, and it often takes too long for these to be patched on end-user devices—if the manufacturer even bothers to release an update, and if the device was even designed to receive them. Companies may cease supporting a device well before consumers have stopped using it. The support period is often not communicated at the time of sale. And sometimes the end of support is not even announced, leaving even informed users unsure whether their devices are still safe. I’ve advocated for the FCC to require device manufacturers to support their devices with security updates for a reasonable amount of time [1]. I can't bring such a proposal