Systems | Development | Analytics | API | Testing

File operations are fundamental when working with data in Node.js. Node.js provides a built-in fs module that allows us to perform various file operations. Whether it's reading from or writing to files, handling different file formats, or managing directories, Node.js offers versatile functionalities to interact with the file system.

With Node.js and Express, you can easily create a JavaScript server. Then the obvious question would be, “Why Typescript?” While JavaScript remains the most popular scripting language, TypeScript emerges as a great alternative when your application becomes more complex or when you collaborate with a distributed team of developers.

Two months into 2024, I’ve decided to summarize the achievements in the Node.js space from 2023. As always, this list is curated by me, so I may overlook some pull requests due to the vast amount of work completed by Node.js collaborators and areas where I need more context, such as WASI. Node.js is rapidly evolving, and it can be challenging for regular users to stay updated with the latest changes. Even as someone who works on the project, it’s possible to overlook certain commits.

In a world full of microservices and distributed systems, building robust and reliable APIs is of paramount concern. One key concept that plays a vital role in achieving reliability is idempotency. In this article, we'll delve into the world of idempotency, exploring what it is, why it's important, and how it can be implemented to solve the persistent problem of duplicate processing in APIs. Along the way, we'll see how to build an idempotent API in Node.js with Redis.

Coming from an HTTP-only background, message queues look very fascinating. Unlike HTTP, you can just push events to the queue and move on. After all, they're a big part of what makes async communication possible between microservices. In this article, we'll take a look at Apache Kafka and how you can build a durable throttling layer with it. Let's get started!

In the digital age, security is of paramount importance, especially when it comes to user data and credentials. As developers, we must ensure that sensitive information, such as passwords, is stored securely to prevent unauthorized access and potential breaches. One of the key techniques employed to enhance security is password hashing, and in the realm of Node.js development, the bcrypt library stands out as a robust solution for this purpose.

Welcome to part two of our series on profiling and optimizing CPU-bound tasks in Node.js! In the first installment, we discussed the complexities of handling CPU-bound tasks in Node.js, shedding light on their impact on runtime performance and exploring various profiling techniques. Once you've used profiling to figure out where the bottleneck in your application is, the next step is to choose the right optimization strategy to obtain an acceptable level of performance for your use case.

The error “Client network socket disconnected before secure TLS connection was established” indicates something went wrong when setting up a secure connection with the server you’re communicating with. This can happen because of an unstable internet connection, wrong security settings on the server, or things like firewalls getting in the way.

Winston Logger is one of the most popular logging libraries for Node.js. This library decouples the different aspects of logging, such as log levels, formatting, and storage, to make them independent and provide an array of different combinations. Additionally, you can implement logging in your application using Node.js streams to minimize performance impact. In this article, we are going to discuss how to install Winston Logger and use it for your Node.js application.