Live data from Hacker News

Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps

electric-sql.com

91–100 of 173 posts

Re: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps

#91
post #75

I saw this recently and I am really excited for, hopefully, a renaissance in local-first apps; it's been quite a long time coming. That said, it seems like there's still a lot of problems to work on in this space and it'll take a while for different approaches and implementations to approach their local maxima. I am curious about encryption. Assuming that ElectricSQL is handling essentially all of the syncing, is it…

Thank you for saying this. I can see this will help app developers to make more apps that can work in airplane mode. More and more we need apps like that. Why do we need internet for an app to work locally on my computer. The whole google, meta, apps are just annoying to require the user to be online to work.

Re: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps

#93
This is a great project.

Also, it reinforces that fact that everyone should pronounce SQL as 'squeal'.

'S.Q.L.' is far too many syllables, and 'sequel' isn't much better. 'Squeal' is just one syllable, so obviously better.

Also, I love how this project now has me singing "OO girl, shock me like an electricSQL".

Re: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps

#94

You might want to update the github star counter on your homepage :-) It said 333 during my visit, while on Github itself it's 1.3K already. Congrats!

Hmm, yes, seems like we might need to bust a cache key there :)

Re: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps

#95
post #93

This is a great project. Also, it reinforces that fact that everyone should pronounce SQL as 'squeal'. 'S.Q.L.' is far too many syllables, and 'sequel' isn't much better. 'Squeal' is just one syllable, so obviously better. Also, I love how this project now has me singing "OO girl, shock me like an electricSQL".

> 'S.Q.L.' is far too many syllables, and 'sequel' isn't much better. 'Squeal' is just one syllable, so obviously better.

I think that "sequel" and "squeal" have basically the exact same consonant and vowel sounds just in different orders.

I mean I know you're making a bit of a joke here, but I'm having fun saying the two words and picking apart the sounds.

Re: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps

#96

I am fully on the offline-first bandwagon after starting to use cr-sqlite ( https://vlcn.io ), which works similar to ElectricSQL. I thought the bundle size of wasm-sqlite would be prohibitive, but it's surprisingly quick to download and boot. Reducing network reliance solves so many problems and corner-cases in my web app. Having access to local data makes everything very snappy too - the user experience is much bet…

Yeah, 1mb of WASM != 1mb of JS.

WASM is much faster to start up since you don't have all the parsing and compiling overhead.

Re: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps

#97
post #94

You might want to update the github star counter on your homepage :-) It said 333 during my visit, while on Github itself it's 1.3K already. Congrats!

Hmm, yes, seems like we might need to bust a cache key there :)

Fixed!

Re: Show HN: ElectricSQL, Postgres to SQLite active-active sync for local-first apps

#100
post #34

I want to be able to have a Postgres database as the central source of truth for all data and user accounts, but then have each users private content to be siloed and synced to their own SQLite database which they alone have access to (maybe even they’re have one SQLite file on server and one SQLite file on phone or etc.). Is this possible with electricSQL? I remember looking at it a year ago or so and was excited bu…

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...

Post reply on HN