Item: MongoDB
Rating: 8
Author: Russell Gomez

Use Cases and Deployment Scope

We use MongoDB as our main operational data store. The application writes directly to the database. We further use it to provide operational reports to our end-users.

Pros and Cons

Flexible schema for changing data elements.
Sharding and replication are seedless.

Setting triggers instead of change stream watcher.
Slowly changing dimension equivalent would be nice.

Return on Investment

On a positive note it has allowed us to rapidly change schemas and add different profiles without needing to go through an extensive data modeling exercise.
On a negative front it is more difficult to insert and retrieve data from MongoDB for the purposes of external partner integration.

Other Software Used

PostgreSQL, Microsoft Visual Studio Code, Notepad++

Once you go the no-SQL route it is very difficult to undo that route. There are other options in the industry that we may consider also including Amazon Dynamo DB. We have considered converting our no-SQL schema to a traditional RDBMS-based email but have found the halfway from here to there very arduous and perhaps not having an ROI that we expected.

Likelihood to Recommend

I believe any startup or any business with a rapidly changing data schema would benefit from using a no-SQL database in general. Analytical and traditional reporting can be difficult to do out of MongoDB or any no-SQL database because the SQL capacity is pretty limited.

MongoDB, powerful flexible and arduous all in one

Overall Satisfaction with MongoDB

Use Cases and Deployment Scope

Pros and Cons

Return on Investment

Other Software Used

Likelihood to Renew

Likelihood to Recommend

MongoDB Feature Ratings