The platform bridging the gap between Node.js developers, operators, and wider business. So you can focus on building 🚀
- Tweets 1,224
- Following 116
- Followers 3,398
- Likes 1,485
Pinned Tweet
🎉 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…
2
9
45
3,703
AI assistants generate bursty, exploratory traffic.
@Spendesk 's MCP tools run inside their @fastifyjs app, trusted internal workflows reuse handlers via mcpCallTool with no loopback HTTP, and Redis-backed sessions survive a switch between production instances.
ALT Platformatic x Spendesk Case Study
1
1
3
142
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.
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?
1
174
Platformatic retweeted
A belief worth correcting:
"we run it in a worker thread, so it's isolated."
A worker thread only isolates the event loop. It does nothing to restrict authority. By default, your worker has full access to the filesystem, network, environment, and process, just like the parent. You changed the location, not the permissions.
Order matters. Permissions must drop before the guest code compiles or imports. If you wait, you create a window where your code has more authority than you planned. That gap is all it takes.
Without checking, can you list every API your dynamic code can access right now?
ALT Introducing secure-eval-worker
1
2
4
154
Deno joined @Cloudflare, and with the runtime winding down over the next year, Luca and Matteo look back at what it leaves behind.
@deno_land pioneered web standards on the server and did the hard work of adapting fetch for @nodejs, collaborated on Node’s own design decisions.
ALT What Deno Gave Node.js
1
1
6
457
@lucamaraschi & @matteocollina will give it an honest postmortem: the two wild bets that didn’t survive contact with reality (URL-based package resolution and the “secure by default” permission model), and why trying them was still the right call.
streamyard.com/watch/UmmnR2J…
1
73
An AI assistant calling a tool has no human to catch a silent response change.
Each of @Spendesk 's MCP tools is built on a Massimo-generated client from their OpenAPI specs, so a contract change is a @typescript error in development or CI, not a broken tool call in production.
ALT Platformatic x Spendesk Case Study
2
2
3
304
Platformatic retweeted
We never planned to build a memcached client.
But every existing option became the bottleneck in our stack. Gateway request deduplication demanded a client that could handle real production traffic at scale. Nothing out there could keep up.
When something sits this close to the hot path, I expect three things: strict opaque-token verification on every response, zero runtime dependencies beyond node:net, and real-world tests against memcached servers with authentication and TLS.
This client delivers on all three.
What’s the slowest link in your stack that everyone ignores?
ALT @platformatic/memcached
1
2
7
293
Jarred Sumner’s argument is that for JavaScript and TypeScript to stay relevant in an AI world, where moving a codebase between languages is suddenly cheap, they have to get as fast as Rust or Go.
ALT No, we should not distribute TypeScript files
1
2
342
@lucamaraschi and @matteocollina work through what that costs.
Wednesday October 21st, 8:00 AM (PT) | 5:00 PM (CEST)
streamyard.com/watch/u6BXNGy…
1
2
139
𝘤𝘢𝘯𝘈𝘤𝘤𝘦𝘴𝘴𝘛𝘰𝘰𝘭 didn't exist in @platformatic/mcp until @Spendesk needed a role check that sees the full request context.
They built it, plus AJV validation, 𝘵𝘳𝘢𝘯𝘴𝘧𝘰𝘳𝘮𝘙𝘰𝘶𝘵𝘦𝘚𝘤𝘩𝘦𝘮𝘢 and 𝘮𝘤𝘱𝘊𝘢𝘭𝘭𝘛𝘰𝘰𝘭, and contributed all of it upstream.
ALT Platformatic x Spendesk Case Study
1
1
2
264
node:vfs is in @nodejs core.
Our follow-up covers what shipped in 26.4, 26.9, and 26.10: new mount model, ZIP provider, native addons, node:ffi, SEA support, --vfs-load.
Plus two corrections to our first article.
blog.platformatic.dev/articl…
2
6
785
memcached has 3 wire protocols.
Most @nodejs clients still use the oldest one: matching error strings, no way to verify a response is actually yours.
The meta protocol (1.6+) fixes this with opaque tokens. We built ours on it exclusively.
Which one does yours use?
Memcached offers three wire protocols. Reality tells us that most @Node.js clients pick the wrong one, and that exact choice has real consequences.
The classic text protocol relies on string matching for error detection. A single typo or unexpected message can silently break your client’s sync. The binary protocol is no longer maintained.
The meta protocol in memcached 1.6 changes the game. It brings compact commands, length-prefixed data, CAS on every operation, and an opaque token with every response so your client always knows it matched the right request. We use it exclusively for a reason.
Anyone can make a fast client. Building one that is fast and never silently wrong is what actually matters.
Is your cache client verifying every response, or are you trusting luck?
ALT @platformatic/memcached
2
270
🎙️ A new Banter episode is coming soon!
@NodeConfEU came back after a year off, new team, new country, and one deliberate decision: 𝐧𝐨𝐭𝐡𝐢𝐧𝐠 𝐚𝐛𝐨𝐮𝐭 𝐀𝐈 𝐨𝐧 𝐭𝐡𝐞 𝐬𝐜𝐡𝐞𝐝𝐮𝐥𝐞.
@lucamaraschi & @matteocollina will debrief the whole thing.
ALT New Banter Episode: NodeConf EU Came Back. Nobody Mentioned AI.
1
2
4
239
Instead of mentioning Ai, it ranged from @nodejs core internals, such as the new Foreign Function Interface or Garbage Collector internals, to an “instruction manual” for the EU CRA, and a Tokio PR.
Register now ⬇️
1
2
105
🎟️ Wednesday October 14th. 8:00 AM (PT) | 5:00 PM (CEST)
🔗 Register now! lnkd.in/gWYsEpSY
49