Review your applications in detail with CPU Profiles in N|Solid and find opportunities for Improve code. You can use the CPU Profiler tool in N|Solid to see which processes consume the most percentage of CPU time. This functionality can give you an accurate view of how your application is running and where it is taking up the most resources.
Writing tests for an application is the most difficult but necessary element of a development process. Tests ensure correct code maintenance and enhanced code quality. In this tutorial, we’ll show the best way to handle side effects in your Node.js applications. But first, let's define side-effects.
When we are executing an application with a significant number of processes, we cannot afford to stop the operation to review what is happening outside of production, for this reason, a tool that allows us to have greater observability and a level of detail is key in the management of our project.
Imagine you are responsible for the health of your node applications and you have N|Solid in place, you would regularly check the N|Solid Console to review your Projects and Applications to quickly view how well things are running.
At NodeSource our mission is to help companies achieve significant time reductions in their processes, allowing them to be more efficient in the performance of their node.js applications. N|Solid is a product, APM —Application performance monitoring — that helps us detect improvement opportunities, detecting vulnerabilities and supporting security, among other amazing features. Something important to note is that we do our magic directly in production.
A few days ago, we were in Texas attending one of the most important events in the Javascript ecosystem. For the first time after these difficult times, we had the opportunity to meet again in person with the main contributors and actors of the Javascript ecosystem on a global scale. The appointment was at OpenJS World 2022. We were really happy to meet again with friends from the OS and NodeJS community, seeing them again was priceless.
A version/environment manager is essential if you work with different Node.js versions—but which should you use? Ayooluwa Isaiah investigates the competing options.
The Data Access Layer (DAL) is the most critical part of any application. This is where the code integrates with an external source of truth like a database. In this take, we'll show you how to build a DAL that talks to Postgres via Node. Then we'll go into best practices like Clean Architecture and what this means in practical terms. Ready? Let’s go! First, a quick note about the code: The code will have modern niceties like TypeScript, unit tests, and will tackle potential scalability issues.
Web applications are necessary to enhance the visibility of a business organization and help them achieve better ROI. Therefore, firms need to choose the right web development language to get the best results. Node.js has emerged as a leading programming language for developing web applications. But in hindsight, there are some complications that developers face with Node.js app maintenance.
At times, Node.js can feel like a black box. Shifting to an asynchronous programming model changes how developers are required to handle and interpret existing data. There are many solutions out there to help the users gain more visibility; however, it has been proved that all those solutions out there to capture such critical information come with a high toll on the performance of every application implementing them.
