MongoDB Reviews

We use MongoDB mainly for data visualization and filtering purposes.

MongoDB's most valuable feature is data visualization.

They could provide more documentation and examples for adding pipeline stages. There could be a feature where commands made in MongoDB could be easily copied and shared in their original format. This functionality would enable seamless transition and compatibility between platforms like Linux and mobile devices, reducing the need for complex filters or Citrix-based solutions.

We have been using MongoDB for five months.

I rate the platform's stability a nine out of ten.

My department has around 50 MongoDB users.

It is a cloud-based version and is simple to deploy.

We evaluated OracleDB and MongoDB. We decided to work with MongoDB as its interface is easier to understand and more universal. It offers ease of integration and simpler configurations compared to OracleDB. It also provides all the essential functionality.

I rate MongoDB a nine out of ten.

We do payroll for government workers. One service we provide is called e-Payslip. You go into the portal, create an account, and download your payslip for the month. If you have to do something that requires you to submit a payslip, you can go to the portal and get your payslip electronically. 

We also have what we call the ESPV. This allows unit managers to validate workers before they are paid for the month. It's an attempt to remove ghost names from the government payroll, so there's a cycle. At some point, somebody who is actually working must be validated in the system, and then the unit head confirms. This is checked by HR before salaries are paid, so you have to be a validated worker before your salary is paid. 

I think that MongoDB isn't too structured, and that's good for our technical team because they are able to search through the database better than if they are using SQL Server.

I feel that most people don't know a lot about MongoDB, so maybe they could add some more documentation and tutorials. In general, I think they should do more to publicize the solution because when I'm in a meeting and I start talking about migrating to MongoDB, people don't know what I'm talking about.

I've worked with MongoDB for maybe two years. In fact, we recently upgraded and moved everything from SQL Server to Postgres and MongoDB. We went live just about a month ago. This was supposed to be the solution to all our problems, and we are in the process of testing to confirm that we are fine. 

MongoDB is stable. 

We mostly used Microsoft databases in the past. We started with Access and Microsoft SQL Server. I've also used Innovation together with SQL Server.

I'll give MongoDB a 10 out of 10. We are getting positive feedback, so far.

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.

My use case for MongoDB is storing logs. Last semester, I worked on a malware and antivirus project, used the deep learning model based on the logs and data from the IDF and FreeRTOS, and stored the logs in MongoDB in a different file.

I store logs in MongoDB for later use, and then I can retrieve the logs and create a model accordingly.

I found that MongoDB is most valuable for storing school-related queries. It's also user-friendly, and I found no difficulty accessing it. Setting it up is easy too.

MongoDB could be more secure.

I've been using MongoDB for one year, but I'm not into creating a full-stack application in MongoDB.

MongoDB is a scalable solution. However, if it's loaded with queries, I can use Docker.

I've never contacted the MongoDB technical support team.

I have experience with MySQL and PostgreSQL, but I'm entirely focused on deep learning, so my team only uses MongoDB and Databricks. I'm not into complicated products, and I know what I can do with MongoDB and how to do it.

The initial setup for MongoDB is basic. It's not complex, but I didn't deploy MongoDB directly into AWS. I used AWS to access the database.

I'm using the free version of MongoDB.

I'm using the database MongoDB.

I'm probably using the latest version of MongoDB because I'm using the latest version of Docker.

I have a team of three working on a project that uses MongoDB.

I recommend MongoDB to others. In my college, almost everyone uses it.

My rating for MongoDB is nine out of ten.

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.

We find the query and speed very valuable.

The performance of the solution could be improved.

We have been using the solution for approximately four years.

The solution is scalable, and we will gradually increase the amount of data stored in the solution.

The initial setup is a little bit complex for cluster deployment. Deployment took a couple of days, including testing.

The licensing for the solution is free.

I rate the solution a seven out of ten.

We primarily use the solution for long-term storage. We use it to store all our data. We also use it to support microservices that already have calculated data. We don't use it for any other purpose.

The most valuable feature of the solution is the ability to easily store documentation regarding structures. 

We can easily connect to MongoDB and search without transformation, without joining. If we want to use a simple search it's really fast. 

The initial setup isn't really that complex.

The solution is pretty stable overall.

If we want to perform some joins or some other types of transformation that are more advanced, in that case, we cannot use MongoDB. We need to use another solution.

The solution needs to better support modern aspects of search engines. There is typically a microservice layer and MongoDB doesn't support well within search engines. If you want to create some complex structures, you need something like Elasticsearch, for example.

The pricing is expensive.

MongoDB should better support small and medium companies. There are a lot of clients out there that are interested, however, they need something lighter and less complex and something not so expensive upfront. 

I've been using the solution for the past two or three years.

The stability of the solution is very good. There are no bugs or glitches. It doesn't crash or freeze. It's pretty good overall.

I've never used technical support. I can't speak to their level of responsiveness or how knowledgeable they are.

We previously mostly used SQL databases. We used Microsoft SQL mostly and we needed some NoSQL databases. That's why we implemented Elasticsearch and MongoDB. We wanted a NoSQL database that we could search, however, was also capable of long-term storage. 

The initial setup is not so complex when we are talking about on-prem solutions. It's an easy initial setup. We are fine with that. 

I was surprised, however, by the lack of support offered during implementation. You are left to your own devices. There isn't much guidance - especially on so complex a transformation.

We have our own agent teams. Mostly we rely on our engineers, not consultants at other companies. We're able to handle everything rather well in-house.

The pricing is quite high and we don't appreciate the solution raising prices so much.

I'm following up with the licensing, however, I don't have the exact figures right now. I mostly advise some companies about that, and usually do not go into detail. What I'm interested in, for example, is when you implement some solution in some company what are the costs for that company in the near future, for example, in one or two years. This is what we are thinking about. 

It's not easy to implement some solutions in some small companies if at the beginning they need to pay some licensing costs upfront. For example, for Mongo DB. It would be easier if the small companies could operate without licensing for some period of time and then only after they grow to a certain size or need they would have to pay some for that usage.

While I may advise clients on MongoDB, I don't have a direct business relationship with the company.

We always use the latest version that is available.

As we implement the solution for clients, we deal with different deployment models. Typically, for banks, for example, the on-premises deployment is used. However, we've looked into the cloud as well and some clients may consider that deployment instead.

A company considering the solution needs to first think about the project and the infrastructure that they need to implement. Every solution is different. I cannot say that I feel some particular way about MongoDB. It always depends on the organizational need. 

I'd rate the solution at a seven out of ten. I'd rate it higher if it offered more upfront support and a lighter solution for smaller organizations. It would be great if they could build an open-source version, for example.