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 selectmethod 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 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 id, name 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

Post a Comment

Popular posts from this blog

How to use Ngx-Charts in Angular ?

Charts helps us to visualize large amount of data in an easy to understand and interactive way. This helps businesses to grow more by taking important decisions from the data. For example, e-commerce can have charts or reports for product sales, with various categories like product type, year, etc. In angular, we have various charting libraries to create charts.  Ngx-charts  is one of them. Check out the list of  best angular chart libraries .  In this article, we will see data visualization with ngx-charts and how to use ngx-charts in angular application ? We will see, How to install ngx-charts in angular ? Create a vertical bar chart Create a pie chart, advanced pie chart and pie chart grid Introduction ngx-charts  is an open-source and declarative charting framework for angular2+. It is maintained by  Swimlane . It is using Angular to render and animate the SVG elements with all of its binding and speed goodness and uses d3 for the excellent math functio...
Post a Comment
Read more

Understand Angular’s forRoot and forChild

  forRoot   /   forChild   is a pattern for singleton services that most of us know from routing. Routing is actually the main use case for it and as it is not commonly used outside of it, I wouldn’t be surprised if most Angular developers haven’t given it a second thought. However, as the official Angular documentation puts it: “Understanding how  forRoot()  works to make sure a service is a singleton will inform your development at a deeper level.” So let’s go. Providers & Injectors Angular comes with a dependency injection (DI) mechanism. When a component depends on a service, you don’t manually create an instance of the service. You  inject  the service and the dependency injection system takes care of providing an instance. import { Component, OnInit } from '@angular/core'; import { TestService } from 'src/app/services/test.service'; @Component({ selector: 'app-test', templateUrl: './test.component.html', styleUrls: ['./test.compon...
Post a Comment
Read more

How to solve Puppeteer TimeoutError: Navigation timeout of 30000 ms exceeded

During the automation of multiple tasks on my job and personal projects, i decided to move on  Puppeteer  instead of the old school PhantomJS. One of the most usual problems with pages that contain a lot of content, because of the ads, images etc. is the load time, an exception is thrown (specifically the TimeoutError) after a page takes more than 30000ms (30 seconds) to load totally. To solve this problem, you will have 2 options, either to increase this timeout in the configuration or remove it at all. Personally, i prefer to remove the limit as i know that the pages that i work with will end up loading someday. In this article, i'll explain you briefly 2 ways to bypass this limitation. A. Globally on the tab The option that i prefer, as i browse multiple pages in the same tab, is to remove the timeout limit on the tab that i use to browse. For example, to remove the limit you should add: await page . setDefaultNavigationTimeout ( 0 ) ;  COPY SNIPPET The setDefaultNav...
Post a Comment
Read more