Skip to main content

WRITING BETTER MONGOOSE QUERIES FOR NODEJS

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 Usercollection to find all users with age greater than 18. Now, our User document might have any number of fields and we might be interested in just displaying the list of 18+ users in the frontend with their names. Then, do we need to pull out details like user.address or user.username? Obviously not. When we only need the name and age, we should only ask for the name and age as we have !
The select chain operator will get the users with only the idname and age fields. This will greatly improve the data being transferred and improve the performance of your application.

2. Use lean()

One thing that can greatly improve your find queries is using the lean() chain operator with your query.
What we know is that Mongoose returns an instance of the Mongoose Document class, which is quite large in size when compared to a Javascript object as it contains a lot of internal features. Now, if we want to get the returned document as just a POJO(Plain old javascript object) we can use the lean chain operator this way ->
Using lean decreases the size of the object being returned which greatly improves performance. A thing to be noted though is that it can only be used for finding and not for anything else! You cannot even keep track or change the POJO to save again. lean() should only be used in operations we do just for reading data.

3. Promise.all

One thing you must be knowing (or should know) is that database queries return a promise. So, usually you would have seen await written in front of the query so as to resolve the promise there and then.
But one of the best things you can do is to use Promise.all() to resolve your promises in parallel which would greatly improve performance of the application as it is equivalent to those queries running at the same time.
This though can only be done if the queries are not inter-dependent and do not need data that the other query brings.
Here, we can see that both the queries are independent and therefore their promises can be resolved in parallel in the Promise.all() function.
These three practices will greatly improve your app’s performance and have no significant negative points so I think you can easily use them in your day to day querying!

Comments

Popular posts from this blog

4 Ways to Communicate Across Browser Tabs in Realtime

1. Local Storage Events You might have already used LocalStorage, which is accessible across Tabs within the same application origin. But do you know that it also supports events? You can use this feature to communicate across Browser Tabs, where other Tabs will receive the event once the storage is updated. For example, let’s say in one Tab, we execute the following JavaScript code. window.localStorage.setItem("loggedIn", "true"); The other Tabs which listen to the event will receive it, as shown below. window.addEventListener('storage', (event) => { if (event.storageArea != localStorage) return; if (event.key === 'loggedIn') { // Do something with event.newValue } }); 2. Broadcast Channel API The Broadcast Channel API allows communication between Tabs, Windows, Frames, Iframes, and  Web Workers . One Tab can create and post to a channel as follows. const channel = new BroadcastChannel('app-data'); channel.postMessage(data); And oth...

Certbot SSL configuration in ubuntu

  Introduction Let’s Encrypt is a Certificate Authority (CA) that provides an easy way to obtain and install free  TLS/SSL certificates , thereby enabling encrypted HTTPS on web servers. It simplifies the process by providing a software client, Certbot, that attempts to automate most (if not all) of the required steps. Currently, the entire process of obtaining and installing a certificate is fully automated on both Apache and Nginx. In this tutorial, you will use Certbot to obtain a free SSL certificate for Apache on Ubuntu 18.04 and set up your certificate to renew automatically. This tutorial will use a separate Apache virtual host file instead of the default configuration file.  We recommend  creating new Apache virtual host files for each domain because it helps to avoid common mistakes and maintains the default files as a fallback configuration. Prerequisites To follow this tutorial, you will need: One Ubuntu 18.04 server set up by following this  initial ...

Working with Node.js streams

  Introduction Streams are one of the major features that most Node.js applications rely on, especially when handling HTTP requests, reading/writing files, and making socket communications. Streams are very predictable since we can always expect data, error, and end events when using streams. This article will teach Node developers how to use streams to efficiently handle large amounts of data. This is a typical real-world challenge faced by Node developers when they have to deal with a large data source, and it may not be feasible to process this data all at once. This article will cover the following topics: Types of streams When to adopt Node.js streams Batching Composing streams in Node.js Transforming data with transform streams Piping streams Error handling Node.js streams Types of streams The following are four main types of streams in Node.js: Readable streams: The readable stream is responsible for reading data from a source file Writable streams: The writable stream is re...