Platformatic

The platform bridging the gap between Node.js developers, operators, and wider business. So you can focus on building 🚀

[Platformatic @platformatic]

Memory vs. performance. Usually gets detected too late.

Next Wed @matteocollina @lucamaraschi :
→ Find the tradeoff at design time, not after
→ What flamegraphs show about Kafka that metrics miss
→ Debug memory. No guessing

Wed 8 am PT / 5 pm CEST
https://t.co/w4U2PJRGFw

[Platformatic @platformatic]

AWS ECS autoscaling reacts after the problem starts.

We benchmarked AWS ECS Target Tracking & Step Scaling against our ICC's predictive scaling.

Results:
Up to 97.8% lower p95 latency
Up to 95.4% fewer scaling actions
Better handling of traffic spikes

https://t.co/hnE21oPfCz

[Platformatic @platformatic]

Four problems. One missing primitive.

→ Can't require() a module from memory
→ Tenant sandboxing requires fragile path logic
→ AI-generated code must hit disk before import
→ SEA assets need 20–40MB of boilerplate

@platformatic/vfs fixes all four. node:vfs

[Platformatic @platformatic]

platformatic/vfs hooks into both fs and the module resolver — in-memory files, tenant sandboxing, runtime code imports, SEA assets.

All transparent to your dependencies.

https://t.co/kycuooqBXA

[Platformatic @platformatic]

If your Node.js rate limiter lives in process memory, it breaks the moment you scale.

@matteocollina & @lucamaraschi will dig down into Rate Limiting in Node.js!

Next Wednesday, June 3rd, 8 am PT / 5 pm CEST →
https://t.co/rMSee0LMa8

[Platformatic @platformatic]

@matteocollina built a module that logs every AI agent mistake to a markdown file.

New session starts → reads the top 30 past mistakes → doesn't repeat them. Not a vector store. A markdown file.

He's running it daily.

Full episode → https://t.co/VvlC4Gqace

[Platformatic @platformatic]

Node.js has 5 ways to call native C. Most teams know 2

→ Native addon changes your build
→ Subprocess adds process boundary
→ WASM only if C compiles to it
→ Microservice adds network hop
→ node:ffi load .so, describe ABI, ~15ns. Nothing changes.

https://t.co/mt47dtRPmw

[Platformatic @platformatic]

Teams wrapping legacy C in a microservice did it because native addons felt too risky.

node:ffi in Node.js 26.1.0 is the option they didn't know existed.

We ran a Doom engine at 35Hz this way to prove it holds

https://t.co/mt47dtRPmw

[Platformatic @platformatic]

Running Node.js on K8s & seeing slowdowns?

CPU limits might be throttling you, even when the node has capacity to spare.

→ Requests vs. limits. Not the same thing
→ How throttling actually happens
→ QoS classes + how to size limits for Node.js

https://t.co/MB4RcT8vVK

[Platformatic @platformatic]

"I built a form library, and then I killed it, and then I brought it back to life again..."

@tannerlinsley on how React Query, and eventually @tan_stack, got built.

Not a plan. A frustration that turned into a tool that turned into a standard.

https://t.co/YICxvDctr7

[Platformatic @platformatic]

Last week, we anticipated "Project Destino", in our weekly banter.

Catch up on the full conversation between @lucamaraschi, @matteocollina and @p_insogna

🎧 Spotify https://t.co/sIHqYEeYQg

🎥 YouTube
https://t.co/XXWOuhpEWN

[Platformatic @platformatic]

We ran Doom in a terminal with Node.js FFI to demonstrate what modern Node.js can actually do.

If Node.js can drive a 35Hz Doom engine with SDL2 audio, it can handle the C libraries your enterprise stack has hesitated to modernize.

https://t.co/mt47dtSnc4

[Platformatic @platformatic]

@p_insogna explains how the "Project Destino" was born and shows us how to run DOOM in the terminal.

https://t.co/Y95ezmSbH2

[Platformatic @platformatic]

Most teams assume K8s handles deployment versioning for durable workflows.

It doesn't.

Deploy a new version, change your step order, and cached results get applied to the wrong steps.

No errors. Just corrupted state.

Platformatic World fixes this
https://t.co/I31fSnaD92

[Platformatic @platformatic]

If your team is stuck on Node 12 and every upgrade conversation ends with "too risky".

Join @lucamaraschi and @matteocollina:
→ Why the Bun Zig→Rust port worked (hint: not the AI) → What AI migration actually requires
→ Node 12 → 24 in practice

https://t.co/h8GNixT6oW

[Platformatic @platformatic]

The real reason we built Regina is as development tooling for our enterprise features. You want to manage agents at scale — Regina is the building block." @Matteo

OSS first. Enterprise foundation underneath. Sequence is intentional.

https://t.co/Qay9xlCZPV

[Luca Maraschi @lucamaraschi]

We Ran DOOM in a Node.js Terminal. Now There's No Excuse for Your Legacy Native Code https://t.co/Wp9VChX8bO

[Platformatic @platformatic]

Four reasons AI agent projects fail after the demo, none of them are the model:
→ Prompts outside version control
→ Sessions wiped on every restart
→ Multi-pod state with no coordination layer
→ Tool workflows with zero observability

Full breakdown: https://t.co/jMICUz3Khv

[Platformatic @platformatic]

Most AI agent failures in production aren't model failures.

They're orchestration failures: no session persistence, no observable tool calls, no lifecycle management.

Regina solves this for Node.js teams.

https://t.co/jMICUz3Khv

[Platformatic @platformatic]

Next week on Banter: we ran @DOOM in a Node.js terminal.

35fps. Sound. One binary. No native addons. No compilation.

@p_insogna built it to prove a point about FFI that every enterprise team needs to hear.

Register now: https://t.co/ys36wOjUmb