ElectricSQL
banner
electric-sql.com
ElectricSQL
@electric-sql.com
Building AI apps? You need sync.

https://electric-sql.com - see also @pglite.dev
Reposted by ElectricSQL
Designed for your existing REST, GraphQL, or tRPC APIs. No backend migration.

Bonus: Works with sync engines (@electric-sql.com, Trailbase, PowerSync) for real-time updates with near-zero incremental network cost.
November 12, 2025 at 10:10 PM
The lesson: by shipping a system that works into production early and learning from it, allowed us to design a much better solution based on real-world requirements.
August 14, 2025 at 3:53 PM
We've been running Electric in production for a year so we knew exactly what we needed: fast append-only writes and no data processing on reads.

The performance gains exceeded our expectations.
August 14, 2025 at 3:53 PM
We're already syncing data to millions of clients in real-time behind a CDN, but our write path was heavily under-optimized.

The result: high CPU usage, accumulating WAL on Postgres, and high end-user p95 latencies.
August 14, 2025 at 3:53 PM
Reposted by ElectricSQL
LangChain, vector databases, instruction routing, specialized memory stores.

You'd be forgiven for thinking you need a whole new stack to build agentic systems. However, that isn't actually the case: electric-sql.com/blog/2025/08...
Bringing agents back down to earth | ElectricSQL
Agentic AI, beneath all the hype, is actually just normal software. You can build agentic systems with a database, standard web tooling and real-time sync.
electric-sql.com
August 14, 2025 at 3:40 PM
We're just magic good sleep enablers! 😎
August 4, 2025 at 5:28 PM
We fixed IPv6 fallbacks, WAL slot recovery, memory leaks, file handle exhaustion, replication races, and dozens more issues.

The boring stuff that makes infrastructure work. Because when AWS launched S3, they didn't lead with features — they led with eleven nines. 🎯
August 4, 2025 at 4:57 PM
Some highlights from our sprint:

• Connection recovery: 18s → 1.2s median recovery time
• Zero-downtime operations: clients stay connected through restarts
• Live schema changes: Electric adapts as your database evolves
• Better observability: see exactly what's happening
August 4, 2025 at 4:57 PM
The results? @triggerdotdev.bsky.social achieved 20,000 updates/sec with sub-100ms latency handling 500GB+ daily Postgres traffic using Electric. Our Cloud syncs data to devices in 100+ countries monthly.

How? Postgres + HTTP foundation + serious reliability engineering.
August 4, 2025 at 4:57 PM
Infrastructure software can't have bugs. Your sync layer is load-bearing infrastructure with database-level expectations.

We looked to S3 (11 nines!) and Redis for inspiration. They're simple ideas made extraordinary through relentless reliability engineering.
August 4, 2025 at 4:56 PM
We look forward to collaborating more to make TanStack DB the future of app development with Electric and the best way to build the new generation of AI apps and agentic systems.
July 29, 2025 at 6:05 PM
It's been a pleasure to partner with @tannerlinsley.com and the @tanstack.com team on this.

HT to @kyle.bricolage.io and @samwillis.uk for leading the work from our side.
July 29, 2025 at 6:05 PM
Paired with Electric, TanStack DB provides an optimal end-to-end sync stack for local-first app development.

electric-sql.com/blog/2025/07...
Local-first sync with TanStack DB and Electric | ElectricSQL
Tanstack DB is a reactive client store for building super fast apps on sync. Paired with Electric, it provides an optimal end-to-end sync stack for local-first app development.
electric-sql.com
July 29, 2025 at 6:05 PM