Electric (Postgres sync engine) beta release
electric-sql.com
Electric (Postgres sync engine) beta release
1–10 of 72 posts
Re: Electric (Postgres sync engine) beta release
#2Is it fair to say that if you have a high read\low write service, you could use this as a sort of local cache (with the added benefit that it also handles staleness through the sync) on the service itself, to reduce latency from not just calls to Postgres but other caches like Redis?
Re: Electric (Postgres sync engine) beta release
#3I may be misunderstanding, but does this boil down to essentially a partial read replica?
Re: Electric (Postgres sync engine) beta release
#4Super excited!
Re: Electric (Postgres sync engine) beta release
#5Informing recent podcast episode with the Electric SQL founder, https://www.localfirst.fm/18.
Re: Electric (Postgres sync engine) beta release
#6I am going to try this, it looks very interesting
Re: Electric (Postgres sync engine) beta release
#7I may be misunderstanding, but does this boil down to essentially a partial read replica?
It's way more powerful than that, since every active user session can have its own shaped & subsetted subscription to live data. See https://electric-sql.com/demos/proxy-auth for an example of how you could build a simple authorization proxy that allows each client session to build a customized long-poll of their own subset of relevant data, directly connecting to the Electric engine, and https://electric-sql.com/demos/react for how simple the frontend code can be.
I fondly remember the days of Meteor (before the pivot to Apollo), where you'd give up SQL and in return be able to give every user a real-time live-updating data model, kept in sync with a secure subset of the central MongoDB database. Now, you don't need to give up the SQL part, nor are you locked into an entire ecosystem. We're going to see really cool things built on this.
Re: Electric (Postgres sync engine) beta release
#8I may be misunderstanding, but does this boil down to essentially a partial read replica?
It's closer to Firebase on Postgres, in my opinion.
Re: Electric (Postgres sync engine) beta release
#9I may be misunderstanding, but does this boil down to essentially a partial read replica?
[deleted]
Re: Electric (Postgres sync engine) beta release
#10I have followed a lot of these projects because I have clients with persistent state and synced state too, as well as realtime needs. Anyway, this passes the smell test imo. It’s solid engineering and built from first principles, reusing the right pieces. So congrats!
My concern with DB startups is always the business model. There’s a massive tension between open source and a sustainable business which is much more prevalent with deeply technical products. So either it’s too open and dies because aws eats their lunch or it’s too closed to be useful for self-hosting, or too complex to self-host, or priced too high for small players. What’s the strategy to build/grow the business in the short-medium term?