MongoDB Reviews

We are using MongoDB for storing user information and our customer data. If an application requires to save information, that data is stored in MongoDB.

MongoDB has helped my organization by being able to handle large amounts of data. Nowadays, if users are using our application all the data we store in our database. If you're trying to receive the information from the database, it's important we are able to retrieve the result as quickly as possible.

The most valuable feature of MongoDB is the NoSQL database. In a SQL database, we need to join data together with a unique ID amongst other things, but in MongoDB, it's not required. We can directly receive all the information. The performance is very good. Additionally, they have frequent updates.

I have been using MongoDB for approximately two years.

The stability of MongoDB is good.

MongoDB is scalable.

We have approximately seven backend developers using this solution.

The MongoDB community support is very good. I was facing some problems using some queries, so I posted my issue on that community channel, and within one day, I received a solution. The support was very quick.

I rate the support from MongoDB a four out of five.

I previously used MySQL and PostgreSQL, but I had permission and licensing issues with MySQL. I prefer MongoDB over others.

The initial setup of MongoDB is straightforward. We only had to use a few commands to install it.

There are different licenses available to be purchased, such as individual, premium, or enterprise.

I did evaluate other options before choosing MongoDB.

Only one person is required for the maintenance of the solution.

I recommend MongoDB to others.

I rate MongoDB a nine out of ten.

We used MongoDB on AWS for a specific project.

We put MongoDB on AWS for a specific project. It's easy to use.

If something is wrong on the cluster, then you need to contact the support team. The stability could be better.

I used MongoDB for about a year.

It's okay. It's acceptable. The stability could be better.

If something is wrong on the cluster, you need to contact the support team. At first, when we were trying to build a cluster.

Neutral

We rated MongoDB a seven out of ten.

Our primary use case of MongoDB was development. We used it from a developer point of view, writing the platforms and storing some data. It was deployed on the AWS cloud. 

One of the first things I noticed when I had my first experience with MongoDB was how easy it was to use. I was expecting more difficulties or at least some challenges, but it was very, very easy to use. It's great technology, performs well, and is very convenient. 

MongoDB is a very useful and convenient choice, but sometimes for more complex projects, there are certain niche requirements that appear, so using a different tool could be beneficial. It raises the complexity of the architecture, but it could be beneficial to the world, the features, the ease of the features which are being implemented. 

My experience with MongoDB is pretty recent, maybe for three years. 

This solution is stable enough. There isn't much maintenance involved—we're just installing some software and then using it—especially since I'm using it from a development point of view. 

I've heard that MongoDB is pretty scalable, but we never did any big deployment. I've read a lot about how it scales and can handle huge data. 

I have never contacted MongoDB's technical support. 

The installation is quite straightforward. I have it installed on my personal laptop and it's very easy to do. It took just a few minutes. 

There are two or three DevOps guys who are involved with and responsible for all the deployments and setups for the whole project. 

I implemented this solution myself. 

We also considered Cosmos DB. 

I rate MongoDB a nine out of ten. If I put it this way: "Can I trust this technology to perform well in a complex project?," I can certainly trust MongoDB. I have been working with some graph databases as well, and MongoDB was my first touch with noSQL technology. I think I like it even more now, after these experiences I had. 

I use MongoDB from a development point of view. For some projects, we use Docker on local environments. MongoDB actually starts in some Docker microservices where we don't run the whole platform, we're actually running locally or maybe part of the platform. With this container, we don't need to do many things with the image in Docker, we're just developing the platform. And then the deployment and scale are managed by the DevOps guys, who do their magic. We use Azure in some projects, but we mostly use AWS. 

MongoDB is a document database that we use for internet applications, logs, and all kinds of things that need quick answers, especially in the document area.

I like that MongoDB has a free version. You can also buy the enterprise edition, which is cheaper than Oracle.

It could be more stable. It would be better if it were more user-friendly like Oracle, which is very easy. For example, creating an index is simple in Oracle. In MongoDB, it's quite challenging to do that.

Performance could be better. It's fast and good, but you cannot put every application that you would like to in MongoDB.

I've been using MongoDB for two or three years.

MongoDB isn't stable like Oracle, but it's okay.

MongoDB is a scalable solution. MongoDB has its own problems, but if you have good maintenance, it's okay. Since it's for internet applications, we can have tens of thousands or hundred thousand users.

There is no technical support since it's a community-supported database. If you would like to buy services like that, there are companies which sell that. But it's not like Microsoft or Oracle, where you have an option of buying support. Instead, there are third-party companies that are willing to provide support for a lot of money.

We switched from Oracle to MongoDB because of costs. Oracle also has a MongoDB solution inside it. In Oracle, you can install document databases, which helps, and it also supports JSON and just about everything. It's one-to-one. Whatever you do in MongoDB, you can do it in Oracle. But Oracle isn't free.

The main problem with Oracle today is the price. Many companies around the world are trying to move out of Oracle because of the cost. They are not moving because the database is not good. PostgreSQL is really like Oracle, and MongoDB is like Redis, and all these have free community databases. If you want to buy the enterprise edition, it costs a bit but not as much as Oracle.

The initial setup is straightforward. Even building the cluster and so on isn't a problem. But you have to know what to do because it's a bit different from relational databases. It only takes a couple of hours and not more than that. Once you have the right servers, firewalls, ports open, and so on, you're good to go.

One or two people are enough to maintain this database. But you'll need more people like programmers for the digital part of the application that you have to develop. 

I implemented this solution by myself.

MongoDB has a free version. You can also buy the enterprise edition, which is cheaper than Oracle.

I would recommend MongoDB to potential users depending on their requirements because it's not a relational database. It depends on what applications would they would like to put in it.

On a scale from one to ten, I would give MongoDB an eight.

We use MongoDB for monthly billing of the mobile software we provide to our client, Talent Post. It includes the services they use on their mobile devices.

One of the biggest benefits is the speed and flexibility of the documents, especially when it comes to modifications. It has definitely helped us to function more efficiently.

The best advantage of MongoDB is the flexibility and scalability of the database.

There is a need for improvement in MongoDB's customer support, better support would be great. 

Another feature that I haven't discovered yet but would be useful is a backup and restore process that can handle large database sizes. Right now, I have over three terabytes of data, including logs, which takes a lot of time for snapshot backups.

I started using MongoDB a couple of months ago.

The overall performance is faster than a relational database like SQL. But, the equation function in MongoDB is not as clever as the stored procedure in SQL. It's more complex to write the functionality like a stored procedure in MongoDB.

I would rate the performance of MongoDB a five out of ten.

I would rate the scalability an eight out of ten. I have around 2500 branches of users that use MongoDB simultaneously. We plan on increasing the usage.

I would rate the initial setup a six, where one is for easy and ten is for complex. It is a little complex. It's more complex when we think about deploying MongoDB with the shopping feature. But setting up MongoDB without consideration of shopping would be easy.

The deployment would take a day, but that includes testing. We didn't use any third parties. We deployed the solution ourselves.

I would rate pricing a seven out of ten. It is a bit costly.

I would definitely recommend using the solution.

Overall, I would give it a seven out of ten. The reason is the flexibility it offers, especially for deploying solutions for mobile services. Additionally, it's still considered a new technology in our country, so it's quite trendy.

I think that MongoDB's search engine should be improved.

My impression is that this is a stable product.

My impression is that this is a scalable product.

When it comes to technical support, I am the same as our reseller. I use community help and google.

My impression is that the initial setup is straightforward.

MongoDB is a fast and safe solution.

I would rate this solution as a whole a seven, on a scale from one to 10, with one being the worst and 10 being the best.

MongoDB's best features are scalability, document management, and data security.

MongoDB would be improved with more integration, particularly for cloud environments like Google BigQuery.

I've been using MongoDB for eight years.

MongoDB's stability is very good.

MongoDB's scalability is one of its best features.

The initial setup was pretty simple.

I would rate MongoDB eight out of ten.

Migrating to MongoDB upgrades the IT environment and puts users in the NoSQL environment, which is faster.

There are some problems with bugs appearing in sharding when the data is too high. MongoDB also needs to update and be more flexible to match up to more mature products like Oracle or SQL.

I've been using MongoDB for three years.

MongoDB is stable and reliable.

MongoDB is scalable.

MongoDB's technical support is quite good.

Previously, I used AWS DocumentDB and DynamoDB.

The initial setup was straightforward, and deployment took around two hours.

We did the implementation ourselves.

MongoDB is a bit expensive compared to its competitors.

I would advise anyone thinking of implementing MongoDB to test the sharding and duplication concepts in your environment with a huge number of data to see how it will work with multiple scenarios or test cases. I would give MongoDB a rating of ten out of ten.