🚀 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. 🧵

The npm team has shipped OIDC publishing from GitHub and GitLab! Has anybody tried it yet? Finally no more npm token leaks! docs.npmjs.com/trusted-publi…

I see the following tweet getting attention. It’s fundamentally incorrect. WebSockets are scalable. There is nothing special about MQTT or any other binary protocol you can invent that make your application scale better. (Differences exists ofc, but not at high level). There are two key drivers: 1. the cost of maintaining a persistent connection in your OSS and infra 2. the capability of your application to offer stateful guarantees while allowing clients to reconnect to multiple servers MQTT semantics provide a fantastic base for this for the 2nd part. Most WebSocket-based applications fail spectacularly at this. WebSocket is a *very costly* protocol, as it cost a relatively high amount of CPU time to decode the messages and encode them again, but you can make it scale very well if needed.

📗 We’ve written the ultimate guide to help you master Node.js. Here's what's inside: 🔄 Do not block the event loop 📶 Monitor Node-specific metrics 🎬 Use Node LTS versions in prod 🤖 Automate testing, code review ⛓️‍💥 Avoid dependency creep