Avoid the complexities of using APIs to move app state over the network. Get super-fast, always-available offline-first/local-first apps.
PowerSync connects to your MySQL database over TCP with read access to all synced tables and permissions to read binary logs (binlogs).
After an initial snapshot of data is taken, PowerSync subscribes to the binlog stream to capture row-level changes.
PowerSync automatically handles most schema change scenarios in MySQL, with no need for client-side migrations.
PowerSync filters the binlog stream based on configured Sync Rules to sync only the relevant tables and rows.
The PowerSync Service tracks changes to data in the buckets, allowing for efficient delta syncing to clients.
You define Sync Rules which determine which data is synced to which users. Data is grouped into buckets which can be shared between users to avoid duplication.
Clients authenticate against the PowerSync Service using JWTs.
The client SDK initially downloads all relevant data and then incrementally keeps it updated, in real time.
Writes are immediately applied locally, and queued for upload to your backend API. The PowerSync client SDK automatically handles failures and retries.
On the client, data is persisted to a SQLite database in schemaless format. The application defines a client-side schema which is applied as SQLite views.
Live reactive queries can be used to update the UI when data changes.
PowerSync uses a server-authoritative architecture with a checkpoint system to guarantee consistency.
Your backend accepts uploaded writes and then applies them to your Postgres database.
