Excellent document-based NoSQL database
February 27, 2020

Excellent document-based NoSQL database

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with MongoDB

We use MongoDB as our primary backend data store solution for our products. We decided to use NoSQL for our project, and MongoDB's document-oriented approach fits our needs and data model very well. It is well supported by many cloud vendors and has been a pleasure to work with for our developers.

Pros

  • Great support by most cloud platform vendors
  • Great developer experience
  • Easy to set up locally for local development, troubleshooting, etc.
  • Excellent library support for popular programming languages
  • Document oriented approach is excellent for data models that can be naturally represented in this way.

Cons

  • Unlike SQL, MongoDB has no joins, which can be an issue in some data retrieval cases, making it less optimal.
  • Not 100% ACID compliant (MongoDB 4 is making improvements, however), although this is also one of the reasons for MongoDB's strength, it would require you to think through your use cases more.
  • The aggregation has a bit of a learning curve.
  • Increased developer productivity due to its flexibility
  • Increased time to market with new features as data structure can be easily changed.
They both could potentially be feasible solutions for us, but in the end, we chose MongoDB because:
  • Relationship and transaction support are not high priorities
  • Better support from our cloud platform vendor
  • Much more scalable, both horizontally and vertically
  • Easier to work with for our developers
As long as MongoDB meets the requirements of our projects, we would continue to use it. MongoDB has also been making staggering improvements, e.g., it now has some transaction support starting version 4.0, so there will be more reasons for us to consider using it in the future.
Depends on the use case, MongoDB may or may not be the best solution. It is not the silver bullet that is going to solve all the database problems. If the use case does require transactions (e.g., financial) or is highly relational, then you would be better off going with the traditional SQL databases such as PostgreSQL. However, if you do not need those, and your requirements lean more towards storing unstructured data, or if your data fits its document-based approach, then MongoDB is a great solution.

MongoDB Feature Ratings

Performance
10
Availability
10
Concurrency
10
Security
8
Scalability
10
Data model flexibility
9
Deployment model flexibility
10

Comments