ElectricSQL Profile Banner
ElectricSQL Profile
ElectricSQL

@ElectricSQL

Followers
6K
Following
1K
Media
37
Statuses
996

Building AI apps? You need sync.

San Francisco, CA
Joined August 2021
Don't wanna be here? Send us removal request.
@ElectricSQL
ElectricSQL
5 months
Tanstack DB is a reactive client store for building super fast apps on sync. Based on a TypeScript implementation of differential dataflow, it's type-safe, declarative, incrementally adoptable and insanely fast 🔥
@tan_stack
TANSTACK
5 months
TanStack DB is now in BETA! We’ve been working on TanStack DB, an embedded, reactive client database for TanStack Query, and are proud to announce today that with the 0.1 release that it's now in BETA!
1
18
138
@samwillis
Sam Willis
18 hours
Querying in @tan_stack DB is incredibly fast and very efficient due to its incremental query engine based on differential dataflow. Updates to the base collection will update the query inside a single frame, often in single digest ms! Awesome demo of this 👇
@kylemathews
Kyle Mathews
19 hours
Another demo — this time processing in real-time the wikipedia events firehose! Durable Streams + TanStack DB + Solid.js handle it with ease
1
3
30
@kylemathews
Kyle Mathews
2 days
New demo of Durable State! A set of building blocks for building real-time syncing systems inside your apps. https://t.co/tUPPmjQbMH
4
24
163
@kylemathews
Kyle Mathews
19 hours
Another demo — this time processing in real-time the wikipedia events firehose! Durable Streams + TanStack DB + Solid.js handle it with ease
4
5
61
@oxfernando
Fernando Abolafio
5 days
Ok, that is interesting. Tell me about a problem worth solving! The amount of boiler plate I need to get this working in cf durable for objects is insane.
@ElectricSQL
ElectricSQL
9 days
Today we're open-sourcing Durable Streams: a persistent stream primitive and HTTP protocol for reliable, resumable, real-time data streaming to clients. We built it inside Electric. Now we're standardizing it as a standalone protocol.
0
2
3
@NathanFlurry
Nathan Flurry 🔩
6 days
🧪 Hacking with Durable Streams + Rivet Actors Actors → the brains & memory Durable Streams → the pipes @ElectricSQL team → the 🐐 This is VERY experimental – demo code & slides below
11
17
142
@cayt3r
Cayter
7 days
Waiting for someone to build a trpc-like fully type-safety experience on top of this and we're done for the next generation of web development.
@tannerlinsley
Tanner Linsley
7 days
👀
2
2
25
@Otota0
Ototao
7 days
Durable Streams = hot reload for your entire backend state.
@tannerlinsley
Tanner Linsley
7 days
👀
0
2
7
@ismasan
ismael celis
7 days
Happy to see an attempt at formalising Durable Streams for HTTP clients.
0
2
5
@gingerhendrixai
Gareth Andrew
9 days
This is exactly the kind of toy I wanted for Christmas.
@kylemathews
Kyle Mathews
9 days
Electric Cloud delivers millions of state changes a day over our durable streams protocol — so we're splitting it out so it can be used for any transport/sync use case. It's a really unique and scalable plain-http protocol that solves a lot of problems we see in AI/real-time.
0
2
6
@schickling
Johannes Schickling
8 days
Very excited to see more libraries and tools focusing on events and streams!
@ElectricSQL
ElectricSQL
9 days
Today we're open-sourcing Durable Streams: a persistent stream primitive and HTTP protocol for reliable, resumable, real-time data streaming to clients. We built it inside Electric. Now we're standardizing it as a standalone protocol.
0
3
29
@kylemathews
Kyle Mathews
7 days
PR #1000 on TanStack DB — https://t.co/Ettau0GBin Coinciding with us zooming past 50k weekly npm downloads
3
4
41
@inazarova
Irina Nazarova
8 days
@thruflo @ElectricSQL Love the open protocol approach!
1
1
3
@csparks1919
Christian Sparks
8 days
as a streaming aficionado, this is pretty cool 👀
@ElectricSQL
ElectricSQL
9 days
Today we're open-sourcing Durable Streams: a persistent stream primitive and HTTP protocol for reliable, resumable, real-time data streaming to clients. We built it inside Electric. Now we're standardizing it as a standalone protocol.
0
1
7
@frankojaker
Frank O. Jaker - e/acc
9 days
massive
@ElectricSQL
ElectricSQL
9 days
Today we're open-sourcing Durable Streams: a persistent stream primitive and HTTP protocol for reliable, resumable, real-time data streaming to clients. We built it inside Electric. Now we're standardizing it as a standalone protocol.
0
1
1
@harrysolovay
Harry Solovay
9 days
Pretty dam cool
@ElectricSQL
ElectricSQL
9 days
Today we're open-sourcing Durable Streams: a persistent stream primitive and HTTP protocol for reliable, resumable, real-time data streaming to clients. We built it inside Electric. Now we're standardizing it as a standalone protocol.
0
1
4
@samwillis
Sam Willis
9 days
Something has been missing from the primitives available for building applications with... a simple URL addressable append only log with a HTTP api. Today we are launching Durable Streams to fix that! Perfect for AI streaming, and state syncing🚀🎉
@ElectricSQL
ElectricSQL
9 days
Today we're open-sourcing Durable Streams: a persistent stream primitive and HTTP protocol for reliable, resumable, real-time data streaming to clients. We built it inside Electric. Now we're standardizing it as a standalone protocol.
1
11
105
@calcsam
Sam Bhagwat
9 days
v interesting
@ElectricSQL
ElectricSQL
9 days
Today we're open-sourcing Durable Streams: a persistent stream primitive and HTTP protocol for reliable, resumable, real-time data streaming to clients. We built it inside Electric. Now we're standardizing it as a standalone protocol.
0
2
17
@kylemathews
Kyle Mathews
9 days
Electric Cloud delivers millions of state changes a day over our durable streams protocol — so we're splitting it out so it can be used for any transport/sync use case. It's a really unique and scalable plain-http protocol that solves a lot of problems we see in AI/real-time.
@ElectricSQL
ElectricSQL
9 days
Today we're open-sourcing Durable Streams: a persistent stream primitive and HTTP protocol for reliable, resumable, real-time data streaming to clients. We built it inside Electric. Now we're standardizing it as a standalone protocol.
3
7
40