I’ve had some hard time when virtuals
wasn’t showing up. Without digging deep into Mongoose, I quickly turned lean
mode off, crafting a new technical debt. After a while, I decided to spend some to look into this particular issue.
This section is also available in my another article.
When lean mode is enabled, all queries return plain JavaScript objects instead of Mongoose Document. In this case, Mongoose will never have to instantiate Mongoose Document from plain JS object, apply magic methods, etc. Neglecting all these overhead in Lean mode, it makes perfect sense to have lean enabled by default.
Virtuals are attributes derived during query, which the values are not actually persisted in MongoDB. Since virtual is one of Mongoose magic attributes, it is disabled by default.
Thanks to the community, I discovered the official plugin — mongoose-lean-virtuals
, which supports virtuals which preserving the behavior of lean mode.
In this article, I will be focusing on how to apply mongoose-lean-virtuals
in a typical Feathers.js Mongoose service (generated with feathers-cli).
First of all, install it:
npm install --save mongoose-lean-virtuals
Suppose we are creating a user
service, we define our model as:
In our model, we defined a virtual uid
to return the Object ID of our user document. Then, we set the properties toObject
and toJSON
to show virtuals. To apply mongoose-lean-virtuals
, we also add in line 20.
In user.service.js
, we add {virtuals: true}
as the value of lean in our service options (line 11).
Try to consume your service, you should be able to see the virtuals now.
Virtual is now available.
According to Mongoose documentation, lean mode is enabled to enhance query performance. However, would applying mongoose-lean-virtuals
affect the performance of our app?
I have done a simple profiling and have the results posted here. Feel free to check it out to understand the performance impact of mongoose-lean-virtuals
.
If you find this article helpful, feel free to give me some 👏 👏 👏 generously.