Revising Node.js fundamentals for a strong backend

⚡️ Day 33 & 34/100: #100DaysOfNode Spent the last two days diving deep into one of the most powerful (and underrated) parts of Node.js — the child_process module ⚙️ Explored how Node lets you create and manage child processes to handle tasks concurrently and improve performance. Learned the differences between spawn() and fork(), their use cases, and how they operate under the hood: 🔹 spawn() — used to run external commands or processes, ideal for continuous data streaming or executing shell commands. 🔹 fork() — a specialized version of spawn(), designed for running separate Node.js scripts. It creates a new V8 instance and includes IPC (Inter-Process Communication) for message exchange between parent and child processes. Understanding these internals gave me a much clearer view of how Node handles concurrency, process isolation, and scalability in real-world systems. Next up 🔜 — combining this knowledge with UNIX tools to explore how real multiprocessing systems tie everything together. 📂 Code & notes: https://lnkd.in/d4NSBpMN #NodeJS #100DaysOfCode #BackendDev #JavaScript #SystemsProgramming #Concurrency #ForkVsSpawn #LearnInPublic #DevJourney

🚀 New TekCast Episode: File-Based Storage — Working with Data Not every project needs a full database! In this episode of JavaScript on the Server, we explore how to persist data using the filesystem in Node.js 💾 You’ll learn how to: ✅ Read and write JSON files asynchronously with fs/promises ✅ Implement CRUD operations ✅ Handle data safely and efficiently ✅ Understand when (and when not) to use file-based storage 🎥 Watch the episode: 👉 https://lnkd.in/gtP5gmsn 💡 Previous TekCasts series: • JavaScript for Beginners: https://lnkd.in/gryqJ7_N • JavaScript in the Browser: https://lnkd.in/gpmjpesm #JavaScript #NodeJS #WebDevelopment #CodingEducation #TekCasts #LearnToCode

🚀 New TekCast Episode: File-Based Storage — Working with Data Not every project needs a full database! In this episode of JavaScript on the Server, we explore how to persist data using the filesystem in Node.js 💾 You’ll learn how to: ✅ Read and write JSON files asynchronously with fs/promises ✅ Implement CRUD operations ✅ Handle data safely and efficiently ✅ Understand when (and when not) to use file-based storage 🎥 Watch the episode: 👉 https://lnkd.in/gAr_xE5j 💡 Previous TekCasts series: • JavaScript for Beginners: https://lnkd.in/g9XxVGmd • JavaScript in the Browser: https://lnkd.in/gp9nxsFi #JavaScript #NodeJS #WebDevelopment #CodingEducation #TekCasts #LearnToCode

I just shipped a new blog🚢: how I turned Docker theory into a lean, practical setup. After a focused week on DCA prep (yes, DOMC turns “quick guess” into “think twice”), I built out a Java service with multi-stage Dockerfiles, Compose for app + DB, and sensible runtime configs: secrets, networks, volumes, logging limits, health checks, and restart policies. Full read 👉 https://lnkd.in/dqHXa2ah #Docker #DCA #Java #Security #Compose

Node.js Streams Explained What Moving the Pyramids Can Teach You About Node.js Streams 🏛️ Imagine you have a 3GB file that you need to upload/download using your Node.js server. How do you solve this task? Your first instinct as a Node.js developer might be to use an npm package. Sounds great to me! But what if I told you that while you're treating the file, you also need to add some business logic? Let's say, for example, the file is a CSV, and you need to keep certain lines and ignore others—while saving the ignored lines in a separate file. Can your npm package handle that? Probably. Is it easier, simpler, scalable? Probably yes. But now you need another package and more complex code in your codebase, which might affect performance. Now let's take a step back. Before downloading the package, did you ask yourself what technique the creators of these packages use under the hood? I'll answer that for you—it's most likely streams, and that's what we're going to talk about in this post. So buckle up, and let https://lnkd.in/gRjYzC_z

Node.js Streams Explained What Moving the Pyramids Can Teach You About Node.js Streams 🏛️ Imagine you have a 3GB file that you need to upload/download using your Node.js server. How do you solve this task? Your first instinct as a Node.js developer might be to use an npm package. Sounds great to me! But what if I told you that while you're treating the file, you also need to add some business logic? Let's say, for example, the file is a CSV, and you need to keep certain lines and ignore others—while saving the ignored lines in a separate file. Can your npm package handle that? Probably. Is it easier, simpler, scalable? Probably yes. But now you need another package and more complex code in your codebase, which might affect performance. Now let's take a step back. Before downloading the package, did you ask yourself what technique the creators of these packages use under the hood? I'll answer that for you—it's most likely streams, and that's what we're going to talk about in this post. So buckle up, and let https://lnkd.in/gRjYzC_z

You are building an application with NodeJS and you have to process a huge data load. You have to put in your consideration the fact that NodeJS is working using the event-loop, which means that the main thread is passing by several phases in order to keep your node program working. This means that if you chose to process this payload without splitting the file on several chunks. your program will freeze until it finishes the processing. This is where understanding how Node truly works makes a difference. So by applying the proposed solution, You’ve built a cooperative scheduler on top of Node’s event loop. Each chunk of heavy CPU work yields back to the loop via the check phase (setImmediate), giving I/O and timers a chance to run before continuing. This helped in preventing event loop starvation and also kept Node responsive during big workloads.

If you have a codebase that uses an older version of Node.js, we have started to put together articles and tools to help you migrate your code. https://lnkd.in/eSQN52vK https://lnkd.in/e5XereSt

⚡️ Day 29 of #100DaysOfNode  Today’s deep dive took me beyond JavaScript and into some powerful low-level C concepts: variadic functions and signal handling. These are foundational for understanding how systems like Node.js manage processes and events under the hood. 🔹 Variadic Functions  Ever wondered how printf() accepts any number of arguments? That’s thanks to variadic functions in C. Using <stdarg.h>, I explored how to build functions that handle a flexible number of parameters—making them highly reusable and dynamic. 🔹 Signal Handling  Signals are how operating systems notify programs of events like interrupts (e.g., SIGINT from Ctrl+C). I learned how to catch and handle these signals gracefully to build fault-tolerant applications that don’t crash unexpectedly. These low-level systems programming concepts are crucial for anyone wanting to understand what's really happening behind frameworks like Node.js. Every layer I peel back brings the bigger picture into sharper focus. 📂 Dive into the code and follow my journey:  🔗 https://lnkd.in/d4NSBpMN #100DaysOfCode #NodeJS #SystemsProgramming   #CProgramming #SoftwareEngineering #DeveloperJourney   #SignalHandling #BackendDevelopment

Task 1/10: Today I built real pagination using: - React + TypeScript - TanStack Query v5 : makes API data easy and smart as it caches, refetches, synchronizes, and manages loading states automatically - Express + MongoDB - Axios for API calls What I learned: ✔ How pagination works (page → skip → limit) ✔ Why backend must validate & cap limit ✔ .lean() improves query speed ✔ Query keys like ["posts", page] make caching easy ✔ invalidateQueries(["posts"]) refreshes paginated pages Github repo : https://lnkd.in/dewmUn7c #Reactjs #Typescript #TanStackQuery #pagination