Systems | Development | Analytics | API | Testing

Node.js is a backend JavaScript runtime built on Chrome's V8 engine that's asynchronous and event-driven by nature. It's relatively simple to create a REST API with Node.js and use frameworks like Express.js. With this simplicity comes a lot of flexibility. However, you can get side-tracked on what patterns to follow when building scalable network-driven applications. This article focuses on some of the patterns and best practices to follow when building Node.js applications.

In this chapter, we'll give you a kickstart introduction to effectively using package.json with Node.js and npm. The package.json file is core to the Node.js ecosystem and is a fundamental part of understanding and working with Node.js, npm, and even modern JavaScript. This file is used as a manifest, storing information about applications, modules, packages, and more.

It’s fair to say that the pandemic has not only wreaked havoc on how individuals live their daily lives but also on how they work. The global changes led to an immediate shift to remote working and unfortunately, not all enterprises were prepared for it. Companies did not have adequate time to prepare and allocate necessary security resources to ensure strong network and device protection for employees working remotely.

Today, npm is a cornerstone of modern web development, whether used exclusively with Node.js as a package manager or as a build tool for the front end. Understanding npm as a tool —particularly the core concepts— can be difficult for beginners. As such, we've written up this guide for getting a grasp on npm, especially for those who are entirely new to Node.js, npm, and the surrounding ecosystem.

The moment you type something on a keyboard, read a file from a disk or download a file over the internet, a stream of information (bits) flows through different devices and applications. If you learn to work with these streams of bits, you'll be able to build performant and valuable applications. For example, think of when you watch a video on YouTube. You don't have to wait until the full video downloads.

TL; DR: Based on the APM benchmarks results is evident that one of the main performance problems for a Node.js application in a production environment is the usage of the very same applications in charge of monitoring the performance for the application itself. This article explains the reasons with an in-depth analysis to show why using most APMs in a Node.js application is that expensive performance-wise.

Node.js error handling isn’t a walk in the park. When deploying applications into production, we want to know that all code has been tested for all possible complex scenarios. We can, however, avoid issues by preparing our code to properly handle errors. To do so, we need to understand: Today we’re going to take you through the above items and give you a tour of JavaScript’s main quirks for better insight and understanding.

If you haven’t checked out the first two-part of our ‘Securing your Applications in Node.js’ series, click here and the second part here. This is a 3-part blog series on Node.js. This article aims to establish a Node.js security roadmap by addressing security challenges comprehensively and consistently for large infrastructures. Let’s begin! 🚀

In this tutorial, you will learn how to add TypeScript support to Node.js projects. Let's get going!

This post describes how I built a realtime collaboration app that scrum teams can use for planning poker. Planning poker, also known as Scrum poker, is a gamified technique for estimating the size of user stories. This helps in deciding how many stories can be put into a sprint. Usually story points in the Fibonacci scale is used as a metric, but T-shirt sizing, like small, medium, and large, is also used.