PowerSync @powersync_

Reflecting on the past year we observe that Sync Streams are bigger and better, and don't remove any existing functionality that users love. Therefore we're comfortable to announce that in T+15 months, legacy Sync Rules will be phased out entirely. releases.powersync.com/announcements/…

The PowerSync Rust/native SDK runs anywhere. Such as your local-first second brain CLI. FlickNote keeps notes on-device for humans and agents, then syncs when you’re back online. github.com/GuionAI/flickn…

Back in May we opened more of our engineering process: more frequent GitHub proposals and Discord engineering discussions. Since then we've seen an uptick in high quality community PRs 🤩 It makes us especially happy to see that the community is enjoying this collaboration

We've started defining the scope for a self-hosted version of the PowerSync Dashboard. If you have any specific feature requests, drop them in comments.

Self-hosting PowerSync? We’ve added a detailed config reference with settings, defaults and examples 😊 docs.powersync.com/configuration/…

Compaction logs are now visible in the PowerSync Dashboard! PowerSync keeps a history of relevant source database changes so reconnecting clients can efficiently catch up. This operation history can become large, so compaction is required. It runs automatically on PowerSync Cloud, now with logs

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. That reduces load on the storage database, improving initial sync speed and stability, especially with large datasets or many clients connecting at once. It also increases capacity for concurrent clients. 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: releases.powersync.com/announcements/…

Incremental Reprocessing One of the biggest pain points with PowerSync was that even a small change to your sync config required re-replicating everything from scratch, and clients had to re-sync all their data. 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. Available for MongoDB sources using Sync Streams. Support for Postgres and other source databases is planned.

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 👇

Checkpoint Requests are now available across all our SDKs. If your app has a mix of online and offline workflows, you probably want to check them out. Our new blog post explores the feature, including a nano case study about how we used them to solve timing issues in the PowerSync Dashboard. powersync.com/blog/checkpoin…

PowerSync @powersync_

a month ago

Sync engines are a fantastic way of automatically keeping your app state up to date with your backend. But sometimes things can get bumpy: datasets explode, infra gets congested, apps get suspended, device's network stack is full of sludge, etc. So we added waitForSync() : a

0 0 2 692 1

New proposal up 👇

Kobie sync/acc @k081e

2 weeks ago

We've opened a proposal to simplify how you connect the PowerSync SDKs to your backend. It would let you choose upload-only, download-only, or two-way sync. It also smooths out several paper cuts 😊 github.com/orgs/powersync…

0 1 4 620 0

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/ad… For Web, Capacitor and Tauri, the transport API gives you the building blocks to create your own: docs.powersync.com/client-sdks/ad…

Our Node.js SDK is now GA, after an extensive ~13 month soak :) V1.0.0 comes with more ergonomic APIs, simpler setup, and a bunch of new features. Release notes: releases.powersync.com/announcements/… Thanks to everyone who reported bugs and feedback during the beta!

We’ve received several customer questions about bucket counting in Sync Streams. We’ve expanded our docs to explain how counts are calculated and added a troubleshooting guide for bucket count and parameter query result limits: docs.powersync.com/sync/streams/b… docs.powersync.com/sync/advanced/…

"We've been getting high PowerSync bills for the past few months", a customer told us. In response, our FDE team created a guide on how to reduce usage and lower your PowerSync Cloud bill: docs.powersync.com/resources/usag…

Custom roles are now self-serve in the PowerSync Dashboard on Team and Enterprise plans. Scope what an org member can view, deploy, and manage, including down to specific projects and instances. Docs: docs.powersync.com/tools/powersyn…

PowerSync Cloud is now infrastructure-as-code. We shipped an official Terraform provider: declare projects, instances & sync config ➡️ terraform apply ➡️ done Docs: docs.powersync.com/tools/terraform AWS ECS example: github.com/powersync-comm…

page: docs.powersync.com/client-sdks/ad…

We recently published a new docs page to help you optimize fronted performance when using PowerSync. Content about debugging + fixing slow queries, as well as fine-tuning sqlite. What else do you want to see on this page?

PowerSync Docs: docs.powersync.com/client-sdks/re… Community Benchmark: github.com/whygee-dev/mem…

A PowerSync community member built a multi-threaded in-memory SQLite connection pool for PowerSync Web. It was waaaay faster than our persistent OPFS options for his read-heavy workload. He published a benchmark: a three-connection pool delivered 49% lower median concurrent-read latency than our single-connection InMemoryVFS. Sequential-query latency was pretty much unchanged i.e. the benefit came from parallelism. Inspired by that work, we built something _even faster_ into the PowerSync Web SDK. InMemoryWriteAheadLogPool runs one designated writer and a configurable number of reader workers over shared database and write-ahead-log buffers. Multiple reads can execute in parallel, including while a write is in progress. This is intended for highly concurrent, online-only workloads with relatively small synced datasets. It is per-tab and non-persistent, requires cross-origin isolation, and trades additional worker startup and memory usage for query concurrency.