Understanding the Limitations of MongoDB
Join the DZone community and get the full member experience.Join For Free
This article from Henrique Weismann (aka Kico Lobo) at /dev/Kico takes an interesting look at MongoDB by highlighting its limitations, not to criticize or demonize MongoDB, but to clarify weaknesses in order to prevent lack of user understanding from misrepresenting it. According to Weismann, "I see the same story repeating itself: people unhappy with it treating [MongoDB's] limitations as if they were bugs."
Weismann's article summarizes each of the areas he considers to be limitations, including:
- Consumption of disk space
- 12-node limit to the replica-set strategy
- Manual changes to master node in the master-slave strategy
- 32-bit MongoDB only handles 2GB of data
In the full article, Weismann goes into more detail and presents a few more limitations beyond these. Again, though, Weismann stresses that this is not a condemnation of MongoDB - these aren't trade secrets, after all, as MongoDB has published their own record of the MongoDB Limits and Thresholds - and it's important to remember that every technology has limitations.
In other words, you can't blame a screwdriver for not being a hammer. Check out Weismann's full article to get a better understanding of the strengths and weaknesses of MongoDB.
Opinions expressed by DZone contributors are their own.