Platformatic

📦 Node.js has fast I/O, but it’s missing a virtual filesystem. That creates real problems: ✔️ Importing modules that exist only in memory ✔️ Diskless testing in CI ✔️ Sandboxing tenant file access ✔️ Running code generated by plugins or AI agents So we built @platformatic/vfs

🎙️New Banter Episode coming soon! Node.js is great at I/O but lacks one key piece: a virtual filesystem.No in-memory imports. @matteocollina & @lucamaraschi will break down VFS, from @platformatic/vfs and what it unlocks. Register now streamyard.com/watch/qjiaVXB5…

Local dev & observability ✅ Run @platformatic/workflow locally ✅ ICC shows live runs, timings, and status ✅ Replay runs on the same version ✅Cancel, inspect, debug Full visibility into workflows. 👉 github.com/platformatic/p…

Version-aware routing & safe draining ✅ Retries (up to 10x) + DLQ ✅ In-flight runs checked before shutdown ✅ Multi-tenant isolation built-in ✅ K8s ready: 2 env vars + 3 labels No code changes. It just works.

🚀 Durable Workflows Beyond @vercel Self-hosted Kubernetes can now run long-lived workflows safely. Platformatic World pins every workflow run to its code version, routes queue messages correctly, and ensures old versions stay alive until work is done. blog.platformatic.dev/durable-workfl…

@saiqulhaq @perpetualtalk @matteocollina @grok If you want to learn more about our Watt, our Blog Post contains multiple articles about it 😉 Here is one: blog.platformatic.dev/introducing-wa…

@perpetualtalk @matteocollina @platformatic I'm curious about it too @grok can you find out?

We benchmarked TanStack Start, React Router, and Next.js running the exact same eCommerce app at 1,000 req/s on AWS EKS. The results were eye-opening.

The takeaway: Framework choice impacts: ✔️ Tail latency ✔️ Stability ✔️ Production risk ⬇️ Full Benchmarks: blog.platformatic.dev/react-ssr-fram…

Under sustained load: 📋 Some frameworks remain stable 📋 Others degrade over time 👉 Consistency becomes the real differentiator

⚔️ React SSR Framework Showdown under real load We benchmarked Next.js, React Router, and TanStack Start at 1,000 req/s. Same app. Same infra. Real production conditions. The results are not what most people expect. blog.platformatic.dev/react-ssr-fram… 🧵👇

This is also a preview of what could land in Node.js core. node:vfs is currently under review. @platformatic/vfs works today on Node.js 22+. When core support lands, switching will be a one-line change. blog.platformatic.dev/why-nodejs-nee…

Use cases where this matters: ☑️ Diskless testing in CI ☑️ Sandboxed multi-tenant systems ☑️ Runtime-generated code (plugins, AI agents) ☑️ Single Executable Applications (SEAs) Basically: workloads where the filesystem shouldn’t be the bottleneck.

📦 Node.js has fast I/O, but it’s missing a virtual filesystem. That creates real problems: ✔️ Importing modules that exist only in memory ✔️ Diskless testing in CI ✔️ Sandboxing tenant file access ✔️ Running code generated by plugins or AI agents So we built @platformatic/vfs

☁️ In cloud-native systems, memory is often the top scaling constraint. We reduced duplication at the runtime layer and cut memory consumption by up to 50%. blog.platformatic.dev/we-cut-nodejs-…

📣 Why is Node.js becoming a key runtime for AI apps? Most production AI systems are orchestration layers handling APIs, streaming responses, and real-time workloads. Join @lucamaraschi & @matteocollina on Node (& More) Banter. 📅 March 18th 🔗 streamyard.com/watch/JxKaAWXD…

🚀 @matteocollina Collina is taking Node.js performance to @cityjsconf London! High-Performance Node.js: Event Loop to Production Observability 4 hours of deep, hands-on learning! 🔗 Limited seats: london.cityjsconf.org

The best part: Frontend teams still use next/image exactly the same way. But platform teams gain performance and operational control. 📊 Internal benchmarks: Up to 40% lower P95 latency during peak traffic. blog.platformatic.dev/scale-nextjs-i…

With Platformatic Image Optimizer mode, image processing runs as a dedicated Watt Application. That means: ✅ Independent scaling for image workloads ✅ Operational isolation from frontend rendering ✅ Centralized validation, retries, and storage

⚡ Scale Next.js image optimization without slowing down your frontend. At scale, /_next/image can become a hidden bottleneck, spiking CPU and slowing SSR and APIs. We built a better approach with Platformatic Image Optimizer mode. 🧵👇