Two very fun meetings this morning with other startups with great use cases for ElectricSQL 🥳

Let's sync data folks!

Tech entrepreneur. Founder @electricsql. Founder @gatsbyjs (acquired by Netlify). @kylemathews on Twitter

Software engineer, creative coder, aspiring generative artist, fridgebuzz.tez/.eth

if you saw the old docs, what we're working on now is http-based so easy to scale with http proxy https://next.electric-sql.com/api/http

I just heard about ElectricSQL. It would have helped with a project I did a while ago but it probably didn’t exist then. Question, though: isn’t websockets going to be expensive if you run this somewhere like AWS? Honest question, I just don’t know.

/max • /bracket • @quickcast • /coys • maxp.co

When shapes are first requested electric queries for the current data from PG and then appends new updates from the replication log.


This means old shapes can accumulate a lot of redundant updates. We haven't yet shipped this but the plan is to compact the log to remove redundant operations.

random q: when a new client comes online, do they have to sync the full history for a given shape? or can they receive a snapshot of the current state and stream from then on?