We just made Next.js 93% faster in Kubernetes. Not a typo. Median latency: 182ms → 11.6ms Success rate: 91.9% → 99.8% How? We stopped fighting the Linux kernel and started working with it. Thread on why your Node.js pods are slower than they should be 🧵

Your Next.js app feels fast locally. Under real traffic while self-hosting? 🔥 Request timeouts spike 🔥 Tail latencies explode 🔥 Random slowdowns appear 🔥 CPU usage makes no sense The culprit isn't your code. It's how rendering fights for the event loop 🧵

🚀 Self-hosting Next.js has just received a massive upgrade! @platformatic Watt v3.18 brings Vercel-level distributed caching to YOUR infrastructure with Next.js 16's 'use cache' directive + Redis/Valkey. No more cache inconsistencies. No more wasted resources. Production-ready scale. Here's how 🧵

Next.js made React development "easy." But self-hosting on Kubernetes? 🔥 Event loop blocked by SSR rendering 💀 One slow component blocks ALL pods 💾 Memory leaks compound under load 🚫 No platform magic to save you Time to face the reality 🧵

Yes, say open source advocates and @platformatic.dev founders @nodeland.dev and Luca Maraschi. They also discussed how React needs to evolve. By @lorainelawson.bsky.social

Ever built a "simple" distributed system that turned into a 3 AM production nightmare? 💀 You started with Kafka (or RabbitMQ) and a few services. Now you're juggling retries, compensations, and correlation IDs like it's a circus act. Time to talk about the workflow orchestration wars 🎧⬇️

🔒 We just shipped application-level file system permissions in @platformatic.dev Watt! The simplest way to segregate your Node.js microservices - leveraging Node.js's native permission model to control exactly what files each service can touch. Here's why this matters 🧵

Don’t comment on individual commits on GitHub. Thanks.

🚀 Noop Functions vs Optional Chaining: A Performance Deep Dive I ran benchmarks comparing `noop()` vs `obj?.fn?.()` and the results surprised me. Spoiler: Noop functions are 5.5x to 8.8x faster. Here's what you need to know 🧵

Having poured my soul into open source since 2008, I was nodding hard at @cory.laviska.com’s post. “It's all take and no give. And I've already given more than enough for two lifetimes.” There’s something especially irritating in watching companies profit off your work without contributing a dime.

🚀 New blog post: "From curl Commands to Type-Safe API Clients" Ever copied curl commands from DevTools to reverse-engineer an API? What if you could turn those into production-ready, type-safe HTTP clients automatically? Here's how 👇

Profiling Node.js used to feel like surgery with a rusty spoon 🩸— kernel tools, V8 magic, pain. Meet @platformatic/flame: zero-config, instant flame graphs. npx flame run server.js → 60 fps insights, no fuss. Performance, democratized. 🔥 @nodeland.dev talk 👉 youtu.be/v7oc80C9vlg #NodeJS #OSS

🔥 BIG NEWS: @platformatic/flame and Watt Runtime now support heap profiling! Finally tackle those memory leaks and optimize your Node.js apps with comprehensive insights into BOTH CPU time AND memory usage. No more guessing where your memory is going 🎯

🎙️ NEW PODCAST: "Node.js Loves Python" What if you could run Python ASGI apps inside your Node.js services? No proxies. No overhead. Just seamless integration. @lucamaraschi & @matteocollina explore how @platformatic/python makes this possible 🚀

🚨 A spurious CVE against fast-redact forced us to rethink everything about log redaction in Node.js The result? slow-redact - a new package that's not actually slow, but guarantees your objects are never mutated Here's why immutability beats speed every time 🧵

#TodayMyPullRequest Make @fastify.dev's etag 70% to 110% faster on medium (2 KiB) to large (2 MiB) inputs: github.com/fastify/fast...

🚨 Another major npm supply-chain attack just hit — and it’s a wake-up call for anyone building on open source. I join @nodeland.dev — creator of Fastify, Node.js core maintainer, and an open-source legend — and Luca Maraschi to break down how attackers are infiltrating npm.

🚀 BIG NEWS: We just shipped @platformatic/python - run Python ASGI apps INSIDE your Node.js process! This changes everything for AI/ML + Node.js apps 🧵 youtu.be/8eAAP9IF4xA

🚨 The npm ecosystem just got hit with another major supply chain attack. If your app uses npm packages (spoiler: it does), you must hear this. We're sitting down with @feross from @SocketSecurity to dissect what happened and how to protect yourself. Thread 👇

🎉 Proud to announce @platformatic.dev is renewing our Open Source Pledge for 2025! We have committed $12,500+ to support the maintainers and projects that power the Node.js ecosystem. Because sustainable open source requires more than code—it requires financial backing.

🎙️ “Be curious and don’t trust everything you read online.” Join our conversation with @nodeland.dev — Co-Founder & CTO of @platformatic.dev, Node.js TSC member, creator of Fastify & Pino, and prolific open source contributor with modules downloaded over 17 billion times a year.

Thanks you @lnugOrg tickets go fast everyone wants to meet and learn from @nodeland.dev and @platformatic.dev - our events next week will be packed! Make sure you get the last few tickets - just 4 left - Final 4 cityjsconf.org/workshops

Remember that thread about Node.js + Kubernetes performance issues? Plot twist: K8s and Node.js are actually a PERFECT match. The problem? Most teams are using 2010 patterns for 2025 architecture. On October 1st, we will discuss how to do it right. Time to level up 🧵

This is the @nodeland.dev effect! He decides to do a workshop in London and this gets #Soldout Register for the free meetup - 30/9 guild.host/events/jsmonth…

Five days until my Node.js workshop in London and this is it - final call for seats If you've been following along for the past 6 weeks, you know this isn't another basic tutorial This Monday, September 29th, we're diving deep into production Node.js 🧵

🚀 Enterprise Node.js apps are powerful but complex. Over-provisioned clusters, slow autoscaling, and disconnected metrics are silently killing your budget and risking outages. What if you could predict problems before they happen? Join us tomorrow, Sep 24th 👇

Open source foundations don’t run on “magic piles of money.” Registries, CDNs, CI pipelines, security response and compliance work all require sustained support. Read why OpenJS joined peers in signing “Open Infrastructure is Not Free.” 🔗 hubs.la/Q03KtFgr0

🚀 BIG NEWS: We just open-sourced the Intelligent Command Center (ICC) for Node.js! After years of watching teams struggle with Node.js on Kubernetes, we're changing the game. The problem? K8s was built for Java/.NET, not Node.js's async model. The cost? 40% overprovisioning. 🧵

We need to talk about Node.js in Kubernetes. The platform meant to deliver elasticity is actually slowing Node.js down and making it more expensive to run. Here's why your "autoscaling" might be bleeding money 🧵👇

Given all the questions about native TypeScript support in Node.js, I should prepare some content to explain it. Maybe somebody already did, and I couldn't find it. Do you know about content explaining it from the user perspective (like how to convert from a compiled app to type stripping)?

ℹ️ Don't know who needs to hear this but npm has had a --before=<date> flag since v6.9.0 (02/2019): github.com/npm/cli/blob/v… Setting a relative date is easy w/: $ npm install --before="$(date -v -7d)" # & only get registry deps that are over a week olddocs.npmjs.com/cli/v11/usin...re

Moving a client's old email system from Meteor + MJML to @fastify.dev + react.email 💌 - Actual @react.dev for templating (w/ Context for nested components) - TailwindCSS for styling - Type-safe props on render (no more failed/missing expansions) Neat.

One week until my Node.js workshop in London and I need to share this urgent production lesson: "Performance optimization without proper measurement is just expensive guesswork" Here's what I mean 🧵

🚨 Ever shipped code that broke in production because an API payload changed? You're not alone. API integration bugs cost teams thousands of hours yearly. But what if your TypeScript compiler could catch these errors before they hit production? Let's talk type safety 🧵

I’m starting to think that sending a security report should come as a bet. If it’s accepted and valid, you get double. If not, you lose it. This would remove so much of the effort on the maintainers side.

The tsc module is the most underrated helper of all LLMs 🤣🥶

And guess what our upcoming workshop with @nodeland.dev on NodeJS Advanced workshop is now #SoldOut - Limited availability for #latebirds

Two weeks until my Node.js workshop in London and here's what I'm hearing from teams who've tried to implement what I teach: "We understand the concepts but struggle with the real-world implementation" Let me show you what I mean 🧵

Join @apollographql.com's MCP Server Builder Series this Thursday in Amsterdam! I'll be there, will you? Incredible lineup, incl. @pimeys.nauk.io, @nodeland.dev, @debergalis.bsky.social, & more 👀

🚨 Your outdated @nodejs version isn't just old. It's a ticking time bomb 💣 Join us tomorrow Sept 10th as @erickwendel.bsky.social reveals the hidden costs and risks of not updating Node.js that most teams don't see until it's too late. streamyard.com/watch/5JqVQrxiwEG2

🚨 Your GraphQL subscriptions are silently losing messages, and you don't even know it. WebSockets give you real-time updates, but when they fail (and they will), your chat messages, notifications, and live dashboards just... vanish. blog.platformatic.dev/resumable-gr... Let me show you how🧵

Just about to go on stage to talk about GraphQL Subscriptions and how to make them reliable!

The npm team has shipped OIDC publishing from GitHub and GitLab! Has anybody tried it yet? Finally no more npm token leaks!

Three weeks until my Node.js workshop in London and I just debugged another "invisible" production issue: "Our API is slow but all our metrics look normal" The problem? They were measuring the wrong things 🧵

🔥 Your Node.js app is slow. You add more servers. It's still slow. You add even MORE servers. Your AWS bill explodes. The problem? You're fighting blind. Time to change the game with continuous profiling that actually works. A 🧵 on how we're fixing this 👇 blog.platformatic.dev/how-continou...

🌐 Reminder from the Node.js TSC meeting today: We're having a Collaborator Summit next October 17th! github.com/openjs-found...

🚀 Today we're shipping Watt 3 - the evolution of our Node.js application server. 15 breaking changes. Months of work. One goal: make Node.js development fast, simple, and production-ready. Let me tell you why this matters 🧵

Pino is now published with provenance. www.npmjs.com/package/pino

🔥 Today we're shipping something special at @platformatic: Next-generation flamegraph visualization for Node.js! We've built a complete profiling ecosystem that makes performance optimization intuitive and actionable. Let me show you what we've cooked up 🧵

Big news! We're launching Massimo - the evolution of @platformatic/client, now battle- tested in production by companies like @Spendesk! From prototype to enterprise-grade: Meet the type-safe API client generator transforming how teams build API integrations. 🧵👇