With PGlite + Electric sync you can build an issue tracker handling 100k issues + 500k comments, synced from Postgres to PGlite in the browser! Super fast UI updates with all writes going though the local database, and Postgres FTS in PGlite for search 🔥

@ElectricSQL Yep, I'll be doing write ups of how to achieve this pattern, along with some other patterns combining @ElectricSQL with other state management systems.

@ElectricSQL So sick! @n_raidenai Sorry to just keep lobbing stuff your way but imagine having this power in the chrome extension. It could reasonable hold every tweet. Would be incredible if I could FTS across every tweet I saw for a day. Maybe let them decay over time?

@ElectricSQL how does the inital sync work? is it like a fetch request which returns thousands of records?

@ElectricSQL Electric uses HTTP GET and long polling for sync. The initial sync is a few hundred mb of JSON (gzips much smaller). The PGlite sync plugin (new version) converts that initial batch to a file to do a COPY FROM for fast import. Ongoing sync converted to normal sql.

@ElectricSQL Impressive numbers! I had the chance to talk with a Rob at the Code BEAM lite in Berlin yesterday. What you are continuously shipping is just mind blowing 🤯

@ElectricSQL Any github link for this demo?

@ElectricSQL Code is here: Will be merged into the main PGlite mono rep once we've fixed a few bugs extracted a few of the tweaks to the sync and live query plaining I've been making.

@ElectricSQL local first FTW!

@ElectricSQL How are you guys thinking about indexDB size limitations? I know zerosync is going for maintaining a windowed cache of your data to get around that issue.