Electricsql
ElectricSQL streams partial replicas of Postgres data to client apps in real time using Shapes, handling the read path with logical replication while writes flow through your existing API. Set up Shape requests with filtering and column selection, implement auth proxies to control access per user, and choose write patterns ranging from online-only to through-the-database strategies.
ElectricSQL syncs Postgres data to local clients in real time using Shapes for partial replication.
AI-generated summary based on this skill's SKILL.md
Install
oakoss/agent-skills/electricsql · repository language: Python
git clone https://github.com/oakoss/agent-skills
cp -r agent-skills ~/.claude/skills/electricsqlgenerated, unverified - the skill's exact subdirectory could not be determined; check the repository on GitHub
npx skillfed install oakoss/agent-skills/electricsqlFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What does ElectricSQL sync database do?
ElectricSQL streams partial replicas of Postgres data to client apps in real time using Shapes. It handles the read path with logical replication while writes flow through your existing API, enabling offline-first applications with automatic synchronization between local SQL databases and your cloud backend.
How does ElectricSQL enable offline-first applications?
ElectricSQL supports offline-first architecture by maintaining local SQL replicas on clients that sync automatically when connectivity returns. The system includes automatic conflict resolution, allowing apps to work seamlessly offline and then reconcile changes with the server without manual intervention.
What is local first SQL database architecture in ElectricSQL?
ElectricSQL's local-first approach stores data locally on each client device using SQL, syncing changes bidirectionally with Postgres. You manage schema changes through your database, set up Shape requests with filtering and column selection, and implement auth proxies to control per-user access to replicated data.
How does ElectricSQL handle real time database synchronization?
ElectricSQL uses logical replication from Postgres to stream data changes to clients in real time. Shapes define which data each client receives, writes return through your existing API, and the system automatically handles consistency across distributed edge and server environments.
Can ElectricSQL replicate data across edge and server environments?
Yes, ElectricSQL replicates data across distributed edge and server environments by streaming Postgres partial replicas to client apps. You choose write patterns ranging from online-only to through-the-database strategies, enabling flexible deployment across edge nodes and central servers.
How do you set up ElectricSQL for local SQL with cloud sync?
ElectricSQL setup involves configuring Shape requests to specify which Postgres data syncs to clients, implementing auth proxies for access control, and choosing your write pattern. The system handles real-time synchronization automatically, managing schema changes and conflict resolution without manual intervention.