Node is an open-source, cross-platform JavaScript run-time environment for developing server-side and networking applications. A peculiar feature of Node.js is its ability to process concurrent requests without delay. It uses an asynchronous programming method for doing so. Usually, when handling a request, the program sends this request to the computer’s file system. It then opens the requested file, reads it and then returns the content to the client.
Architecting a maintainable, readable, and reliable codebase is important not only for the people who will work on the code after you, but also for your own sanity. I’ve worked on dozens of production Node.js backend services and will share my experience of architecture pitfalls to avoid when building yours.
As unpleasant as they are, errors are crucial to software development. When developing an application, we usually don't have full control over the parties interacting with a program and its hosts (including operating system versions, processors, and network speed). It's important you have an error reporting system to diagnose errors and make errors human-readable. In this post, we'll first look at the two common types of errors.
The Node.js team recently announced the release of version 19. This has the following features: In this article, we will explore the major highlights of this release. We recommend downloading the latest Node.js 19 release to follow along. To verify your version of node: Let's get started!
Node.js 18 was released on the 19th of April this year. You can read more in the official blog post release or in the OpenJS Blog announcement. The community couldn't be more excited! If you want to lend a hand, we welcome your ideas or solutions contact us, or if you would like to help us continue supporting open source, you can contribute with an issue here.
As we mentioned in the previous article, at NodeSource, we are dedicated to observability in our day-to-day, and we know that a great way to extend our reach and interoperability is to include the Opentelemetry framework as a standard in our development flows; because in the end our vision is to achieve high-performance software, and it is what we want to accompany the journey of developers in their Node.js base applications.
JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. JSON is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages (C, C++, JavaScript, and so on). These properties make JSON an ideal data-interchange language.
Recently, conversations have been increasing around OpenTelemetry; it is gaining more and more momentum in Node.js development circles, but what is it? How can we take advantage of the key concepts and implement them in our projects? Of note, NodeSource is a supporter of OpenTelemetry, and we have recently implemented full support of the open-source standard in our product N|Solid. It allows us to make our powerful Node.js insights accessible via the protocol.
Job scheduling is the process of starting a job, task, or function at a specific time or when specific events take place. Cron, the time-based job scheduler used in Unix-like systems, is the basis for the majority of job schedulers. Numerous job schedulers are available for the Node.js runtime environment. While some of these schedulers operate in both the browser and Node, others exclusively in Node.
Do you have a Node.js project that you want to put into production but don't know how? In this tutorial, you'll learn how to deploy a Node.js and MongoDB application to Heroku. Before we get started, let's take a very quick look at Heroku and MongoDB.
