MongoDB - the game changer
September 12, 2017
MongoDB - the game changer
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with MongoDB
As a consultant I am working on our latest project as Solution Engineer and Dev Team Lead. MongoDB is used to save configuration data of any kind of device used in the scope of the company (a kind of CMDB). This data is structured by device, so in best case we can talk about semi structured data for a database perspective. To handle this it needs a flexible schema or a base set of relational tables surrounded be exception tables. Both would work to save the data. But when it comes to make use of it, the flexible schema of MongoDB pays dividends. Queries are much faster, and any adoption of a new device can be done with almost no impact, whereas we would need to define a further exception in the relational model.
Also the development turned out to be leaner since we could simplify the queries, and API.
Also the development turned out to be leaner since we could simplify the queries, and API.
- Replication is a real plus; it is shipped out of the box and a simple three-node replication set can be setup with a few commands in less than 5 minutes.
- Sharding steps in the same direction as replication, just more complex - what is in the nature of the issue since we are talking about distributed databases.
- MonogDB is light and easy to run and administer
- Monitoring is still a little bit difficult, though the latest releases of Compass (MongoDBs Monitoring tool) have led it to catch up.
- Implementation time could be speeded up
- Lowers the cost for hardware due to horizontal scaling
- It takes some time to really get really into the business and do a deep dive
I tried Cassandra, but the performance lags behind MongoDB