Some people in Latin-America may remember an old Yupi ad where a woman was complaining on how difficult using the internet was. “It’s so difficult. So complicated! There must be something better.” (In Spanish, of course.) Cheesy as it sounds, Händel Messiah’s “Hallelujah” sonorously invaded the screen. Don’t believe me? See for yourself.
That’s how I felt when I was investigating what’s the best approach to achieve faceted searches in MongoDB. But I found something better. Let me show it to you.
For a project that I had been assisting with for a while already, the need for performing faceted searches came up. I haven’t done this before with MongoDB but – how hard could it be, right? I went out searching for the best practices on the subject, only to find contrived examples and approximations that didn’t account for all situations. Most solutions had limitations here and there. Not only downsides, but straight down cases that would not work, and some others weren’t even worth the effort for the maintainability nightmare that they would have caused. Some other solutions for that were already part of paid products, which is not something that we could use for this project (you know, small pet projects and so on).
So I stepped onto it and came up with a simple and reusable solution: mongo-faceted.
What is faceted search?
If you reached here and don’t know what faceted search is, don’t worry my friend, I can deliver that to you in a painless simple explanation. Think of it as “intelligent filters”, although there is a little bit more to them, conceptually.
When you search google for “cars”, you will get a list of results. You can think on this search as performing a filter: you’re telling Google to give you, from the set of all the results that it could provide, only those that are related with cars. You just performed a filter. (Congratulate yourself quickly and keep reading.)
When you switch to Google Images, you have performed yet another filter: you’re telling Google to provide results related with cars AND those that happen to be images. Before you can congratulate yourself again, you may have noticed that the toolbar can help you find what you’re looking for, with options that seem to be a little more intelligent: options that make sense for images, for example, their color.
This type of filter makes no sense for things that are not images.
You may have noticed this pattern already: if you enter the computer departments in Amazon, the filters may show something like the processor type or the screen size. And furthermore, it gives you the options that are available. This is called faceted search: the system gives you the available attributes and the possible set of values for those attributes. These are called facets.
If the system is intelligent enough, it will help you in not making combinations that will return nothing, because that’s useless to you, seeing an empty page is not probably what you were looking for.
If you’re interested in this pattern and its best practices, I suggest you stop searching for cars in Google and read these great articles:
- Design Patterns: Faceted Navigation, from A List Apart
- Filters vs. Facets: Definitions, Norman Nielsen Group
- Faceted Navigation, Patterns in Interaction Design (Wellie.com)
- Faceted Search, Wikipedia
mongo-faceted is a library that you can incorporate in your own code which allows you to perform faceted searches and get results on what that search allows to filter.
Here you can see an example of how it can be used:
As you may have already guessed, mongo-faceted performs two slight modifications:
- It adds the
searchWithFacetsmethod as a static method to the model you were defining. All other methods are left untouched and will work as usual.
- When calling
searchWithFacetsit will return the usual results and also include a property called
facets. This property will include all available facets and their values.
mongo-faceted will detect the structure of your schema and add the proper logic to your model. Invoking this functionality is just one line:
If you happen to find any issues or limitations, feel free to report an issue on the repository, or submit pull requests (definitely welcome!).
How it works
mongo-faceted works a very simple way: it performs a search, and then performs a second search aggregating results. This is a linear approach to the generally recommended approach of performing a single call for every property in the schema, facilitated by MongoDB’s aggregation framework.
The aggregation call has basically this structure:
originalSearchFilters, so that it applies on the same set of results
$unwindstep for every array property in the schema, so that they can be reported together
$addToSetfor every property, so that all possible non-duplicate values are reported as available for a specific property
You can also see how the approach can be applied without the library, which was basically a proof-of-concept that I worked on before making this reusable as a library.