Node.js is based upon an event-driven, light-weight, and non-blocking I/O model. This is a lightweight, minimal framework based on the Google Chrome V8 engine . The Event-loops are the soul of event-driven programming, almost all the programs using UI use event-loops to detect and react to the user events. Like Clicking a button, Ajax Requests, etc. Node.js is a command-line tool(See getting started with Node ). It is a high-performance network application, JavaScript minimal framework well suitable for the concurrent environments. Node is not just JavaScript, its major part is written in C/C++ . Node.js Architecture Node uses event-loops by JavaScript callbacks to implement the non-blocking I/O. (We must always keep in mind that JavaScript used in Node is not exactly same as we know, it is different, in fact, it is no DOM implementation used by Node, so be careful). Everything inside the Node runs upon a single thread(main thread) , ...
Posts
Performance plays a big part in any application and one of the most vital parts in any application’s performance is it’s queries. Therefore, it becomes absolutely vital to write better mongoose queries if you are creating a NodeJS application. I work with a team of great developers and have learned a lot of tips and tricks for writing better queries overtime. In this article I will share some of my favourite best practices to write better mongoose queries that will improve the performance of your node application. 1. Use Projection It is really important to query for only the data fields that you need , i.e, we should not bring the data from the database that will not be used by us. Mongoose provides us with a select method that will only bring certain fields with the documents when we query over the collection. In the above query, we query over the User collection to find all users with age greater than 18. Now, our User document might have any number of f...
Increase SSH Connection Timeout On the server, head over to the /etc/ssh/sshd_config configuration file. $ sudo vi /etc/ssh/sshd_config Scroll and locate the following parameters: #ClientIntervalAlive #ClientAliveCountMax The ClientIntervalAlive parameter specifies the time in seconds that the server will wait before sending a null packet to the client system to keep the connection alive. On the other hand, the ClientAliveCountMax parameter defines the number of client alive messages which are sent without getting any messages from the client. If this limit is reached while the messages are being sent, the sshd daemon will drop the session, effectively terminating the ssh session. The timeout value is given by the product of the above parameters i.e. Timeout value = ClientIntervalAlive * ClientAliveCountMax For example, let’s say you have defined your parameters as shown: ClientIntervalAlive 1200 ClientAliveCountMax 3 Increase SSH Timeou...
Google ReCaptcha v3 in Nodejs In this node js google v3 recaptcha example tutorial, we will use Node.js and express framework to build a Google v3 Recaptcha Security. 1. Get Google reCaptcha v3 credentials Now, you need to register your site with this URL: https://www.google.com/recaptcha to get the API key and API secret. Note:- Google Captcha does not natively support the localhost domain so what you need to do is in the text box of the site name, put your local address: 127.0.0.1. That is it. 2. Create a fresh project Here you need to create project folder and then type the following command into your command prompt (cmd): mkdir public npm init We are initializing the package.json file. { "name": "googlerecaptcha", "version": "1.0.0", "description": "", "main": "server.js", "scripts": { "start": "nodemon server" }, "author": "tutsm...
I’ve always wanted to build an API, but was scared away by just how complicated things looked. I’d read a lot of tutorials that start with “first, install this library and this library and this library” without explaining why that was important. I’m kind of a Luddite when it comes to these things. Well, I recently rolled up my sleeves and got my hands dirty. I wanted to build and deploy a simple read-only API, and goshdarnit , I wasn’t going to let some scary dependency lists and fancy cutting-edge services stop me ¹ . What I discovered is that underneath many of the tutorials and projects out there is a small, easy-to-understand set of tools and techniques. In less than an hour and with only 30 lines of code, I believe anyone can write and deploy their very own read-only API. You don’t have to be a senior full-stack engineer — a basic grasp of JavaScript and some experience with npm is all you need. At the end of this article you’ll be able to deploy your very own API...