PowerSync

We love SQLite, but working with booleans can have some rough edges due to SQLite's absence of a dedicated bool type. We shipped "fixed_booleans_in_json" in 1.27 of the PowerSync Service, which now preserves boolean literals in synced JSON. Check it 👇

We've released 1.27.1 of the PowerSync Service on Docker Hub. It contains mitigations for the eMudhra Intermediate CA Compromise. The compromise could affect JWKS fetching and TLS connections for source databases. It is recommended to upgrade now. github.com/powersync-j...

Sometimes your app requires fast user switching. If you call disconnectAndClear(), then each time a user switches they need to re-download all their data. To make user switching faster, consider preserving local data when disconnecting: db.disconnectAndClear({ soft: true })

Usage guidance: docs.powersync.com/resources/u...

PowerSync Service 1.26.0 is out, introducing storage version 4 with two big improvements: - Incremental reprocessing for MongoDB - S3 object storage for bulk sync data TL;DRs below 👇

Storage version 4 and S3 are rolling out automatically to Free plan instances. Other plans can opt in, with S3 enabled separately. The upgrade involves a one-time full client re-sync. Rollout details and setup instructions:

PowerSync Service 1.26.0 is out, introducing storage version 4 with two big improvements: - Incremental reprocessing for MongoDB - S3 object storage for bulk sync data TL;DRs below 👇

Bucket storage on S3 When enabled, larger batches of sync data move from the instance’s storage database to S3. The Service reads them from S3 and streams them to clients.

PowerSync Service 1.26.0 is out, introducing storage version 4 with two big improvements: - Incremental reprocessing for MongoDB - S3 object storage for bulk sync data TL;DRs below 👇

With storage version 4, most Sync Streams deploys reprocess only the streams you’ve added or changed. Clients only re-download data for those affected streams. Some changes still require a full reprocess, but routine config updates become much lighter.

PowerSync Service 1.26.0 is out, introducing storage version 4 with two big improvements: - Incremental reprocessing for MongoDB - S3 object storage for bulk sync data TL;DRs below 👇

Large attachment transfers just got easier in our JavaScript SDKs: you can now avoid buffering entire files in JS memory

Expo, bare RN & Node.js get streaming-capable filesystem adapters with ready-made transports: docs.powersync.com/client-sdks...

The new OPFSWriteAheadVFS for wa-sqlite not only brings concurrent reads to SQLite on the web, but also makes write transactions faster!

In plain English: NORMAL/OFF = faster but may lose latest writes; FULL/EXTRA = safer but slower.

The new OPFSWriteAheadVFS for wa-sqlite not only brings concurrent reads to SQLite on the web, but also makes write transactions faster!

So the tradeoff is simple: faster writes now, weaker crash protection for newest data. This is often fine for local-first apps where recent changes can be retried, re-synced, or recreated from server state.

The new OPFSWriteAheadVFS for wa-sqlite not only brings concurrent reads to SQLite on the web, but also makes write transactions faster!

In default mode, commit means "this transaction is recorded in WAL and the database stays valid," not "the browser has definitely flushed this to storage." If the tab crashes or the device loses power, the app may lose the most recent writes, but the database should not come back corrupted.

The new OPFSWriteAheadVFS for wa-sqlite not only brings concurrent reads to SQLite on the web, but also makes write transactions faster!

It does this by not insisting every commit hit the disk immediately. Instead of updating the main database file right away, it writes changes into side log files first. That is cheaper, so small write transactions finish much faster.

How would you like a persistent browser database that: 💾 stores data durably in the browser 🪶 avoids Asyncify time and size overhead 🌐 skips COOP/COEP header requirements 🗂️ works across multiple tabs and workers 👀 supports simultaneous read transactions

📝 supports write-ahead logging (WAL) ⚡ moves data faster than IndexedDB ✍️ commits writes faster than IndexedDB 📁 lets you copy, import, export, and rename DB files with OPFS? Say hello to OPFSWriteAheadVFS, a new virtual file system option for wa-sqlite!

If your AI app needs durable runs, resumable streams, background jobs, and shared history to be reliable, you're already partway to multiplayer. The next step is making that state collaborative so that your agents can align with not just a single user, but an entire team.