Twitxy Saved

Platformatic

@platformatic

The platform bridging the gap between Node.js developers, operators, and wider business. So you can focus on building πŸš€
platformaticHQ.com Joined April 2022
116 Following 3.4K Followers 1.2K Posts

Latest posts 5

Pinned post

Platformatic @platformatic
πŸŽ‰ Introducing sqlite-js-stream: Litestream, rewritten in TypeScript for @nodejs.

Same LTX format; runs inside your process as an npm package. No sidecar, no extra moving parts.

Written by an AI agent, reviewed by a human.
blog.platformatic.dev/sqlite-js-stre…
blog.platformatic.dev sqlite-js-stream: Litestream Rewritten for Node.js Discover sqlite-js-stream, a TypeScript port of Litestream for Node.js that streams SQLite backups with bounded memory and S3 replication support.
2 replies 9 reposts 47 likes 4.3K views View on X
Platformatic @platformatic
πŸ“’ πƒπžπ©πžπ§ππžπ§πœπ’πžπ¬ π€π«πž 𝐍𝐨𝐭 𝐭𝐑𝐞 𝐏𝐫𝐨𝐛π₯𝐞𝐦

The same Brotli decoder bug hit Node, Bun, .NET, Envoy, and Istio at once.

@jarredsumner of @bun reads that as proof that dependencies are over.

streamyard.com/watch/rEv8sSXd…
streamyard.com Dependencies Are Not the Problem The same Brotli decoder bug hit Node.js, Bun, .NET, Envoy, and Istio at once. Jarred Sumner of Bun reads that as proof that dependencies are over. His view is that rewriting a dependency is now one...
Platformatic @platformatic
Moving untrusted code into a worker thread isn't sandboxing it.

A worker isolates the event loop, not authority: it still starts with filesystem, network and process access.

If you want a narrower boundary, you have to drop those permissions before the guest code compiles.
Luca Maraschi Verified account @lucamaraschi Oct 20
Meet sqlite-js-stream: Litestream, rewritten for Node.js in TypeScript

It speaks the same LTX format as Litestream, so the two can read each other's files. Stream your SQLite WAL directly to S3 or local storage, and restore from it.

But the real breakthrough is not just the port. It's how you deliver it. Litestream requires a Go sidecar, its own config, and a separate binary to manage on every deploy. sqlite-js-stream is an npm package that runs inside your Node.js process. No sidecars, no extra moving parts.

That sidecar overhead? It's the main reason SQLite hasn't seen wider adoption in production. Matteo called it, and I agree.

Here's the kicker: the entire port was built by an AI agent running locally on two DGX Sparks, with a human in the loop for planning, review, and final decisions.

If SQLite backups were just one npm install away, would you finally run SQLite in production?
View quoted post on X