



Mar 26 · 15 min read · What If Node.js Could Have Zero-GC Request Handling — Without You Changing a Single Line of Code? A Proposal for a Hybrid Arena + GC Memory Model Baked into the JavaScript Runtime The Problem Nobody
Join discussionMar 14 · 4 min read · In the world of backend development, Node.js is often praised for being "fast" and "asynchronous." But as engineers, we need to look past the marketing terms. How does a single-threaded environment ou
Join discussion
Mar 9 · 4 min read · As JavaScript developers, we often praise the language for its flexibility and Developer Experience (DX). We don't have to worry about pointers, memory allocation, or strict typing. But under the hood
Join discussion
Feb 18 · 18 min read · Somewhere in AWS us-west-2, a Node.js cluster is running. Six replica pods. 2 GB memory per pod. Half of that memory is pointers — 64-bit addresses pointing to other objects, arrays, closures, and strings. Not your data. Not your business logic. Just...
Join discussion
Feb 10 · 5 min read · Node.js applications are fast and scalable, but long-running servers often fail due to one silent killer: memory leaks. These leaks slowly increase memory usage, degrade performance, and eventually crash servers. In this blog, we’ll explore how Node....
Join discussionFeb 7 · 22 min read · If you asked a kid what FizzBuzz is, they'd probably tell you it's a game they played at school. The teacher would corral them into a circle, and they'd start counting numbers out loud in a clockwise fashion. For every number divisible by 3, they'd s...
Join discussion