PowerSync

1.5K posts

PowerSync banner
PowerSync

PowerSync

@powersync_

Sync engine for keeping backend databases in sync with in-app SQLite. Postgres | MongoDB | MySQL | SQL Server 🐘🌿🐬🛢️«-» 🪶

Distributed Katılım Mayıs 2023
781 Takip Edilen2.2K Takipçiler
PowerSync
PowerSync@powersync_·
@rodydavis 👍 What's your sentiment on the overall stability of OPFS in Chrome?
English
1
0
0
23
Rody Davis
Rody Davis@rodydavis·
@powersync_ I do file blobs with OPFS and a POSIX metadata layer with indexedDB. That way I get super fast file/folder manipulation and can support symlimks while heavy ready/write blob streaming is done via OPFS and can even deduplicate.
English
1
0
0
125
PowerSync
PowerSync@powersync_·
Persistence on the web in prod?
English
1
0
2
392
PowerSync
PowerSync@powersync_·
If the app needs stronger guarantees, it can turn durability back up with PRAGMA synchronous=FULL or EXTRA. Then the VFS flushes more aggressively so recent commits are much more likely to survive crashes, but write performance drops. In plain English: NORMAL/OFF = faster but may lose latest writes; FULL/EXTRA = safer but slower.
English
1
0
1
110
PowerSync
PowerSync@powersync_·
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.
English
2
1
12
1.1K
PowerSync
PowerSync@powersync_·
We're at @stirtrek! Come say hi, grab a free tshirt, enter a giveaway for a Meta Quest 3S, and chat about building fullstack AI applications
PowerSync tweet media
English
0
1
4
1.4K
PowerSync
PowerSync@powersync_·
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!
English
3
2
22
5K
PowerSync
PowerSync@powersync_·
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.
PowerSync tweet media
English
1
1
5
627
PowerSync retweetledi
PowerSync retweetledi
Dev Agrawal
Dev Agrawal@devagrawal09·
I've been taking all my learnings of building AI applications of the past 14+ months and distilling them into a single blog series Starting with this first post, with many more to come
PowerSync@powersync_

Building AI apps isn't just about calling an API. It’s a fundamental shift in system architecture. We just published Part 1 of a new series on AI Engineering: The New Primitives. 🧠 LLMs as probabilistic functions 🛠️ Tool calling vs. APIs 🏗️ Context engineering

English
0
3
18
2K
PowerSync
PowerSync@powersync_·
Shoutout to Roy Hashimoto for putting the work into improving the state of the art of SQLite on the web 👏 Full discussion - github.com/rhashimoto/wa-…
English
0
0
2
188
PowerSync
PowerSync@powersync_·
To keep multiple tabs and workers in sync, connections send lightweight messages over BroadcastChannel after commits and checkpoints. They also use navigator.locks to advertise which range of WAL history each connection still needs. Result: browser SQLite that behaves much more like a normal SQLite WAL database under concurrent reads.
English
1
0
1
201
PowerSync
PowerSync@powersync_·
wa-sqlite now supports concurrent readers + a writer in Chromium, unlocking some massive performance gains for certain situations. How does this work? OPFSWriteAheadVFS avoids direct writes to the main database file during normal transactions. Instead, a writer records changed pages in separate log files first. That means readers can keep using a stable view of main DB plus any already-known newer pages, instead of fighting writers over the same file state.
English
2
6
27
6.5K