MongoDB Reviews

Our primary use case has been for maintaining video content and varying it. We are an enterprise-level organization with around 500,000 employees internationally. The company has over 10,000 users of this solution. I'm an integration solution architect. 

The solution is user-friendly with a good object retrieval feature. There are no joins, queries are fast and the product provides helpful drivers. I like the abstraction layers. 

I'd like to see improved scalability and elasticity. Also, the software should have certified container images so it can readily be used in production.

I've been using this solution for two years. 

The solution is stable. 

More could be done to improve the scalability.

Customer support is at a reasonable level. 

The initial setup was pretty simple. It's a good product for academics since it's an open-source solution so it's readily accessible with fast onboarding. Deployment was carried out in-house. There is no maintenance required.

I rate this solution seven out of 10. 

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.

We use it as a data warehouse, and we also use it for software development when we are not sure how much and what kind of data we would get from the customers. For a short span of time, we also use it for the data lake to dump the data of a temporary instance so that the developers on the next node can leverage this data.

I like the schemaless architecture that it follows. I also like the sharding that it provides.

Its security features can be better. Sometimes, my higher authority says that we are not going to use MongoDB because it doesn't provide that much security for the RDBMS or relational data that we use for transactions. Instead of MongoDB, we will use Oracle Database because for a transactional service, you have to rely on RDBMS ACID properties.

I would love to work on MongoDB by using my mobile phone. When I am working remotely or traveling and have some instances deployed on my server, I should be able to check through my mobile whether all the data is being pulled. GitHub has a similar feature, where it lets you read from the laptop, and you can also pull and push with your mobile phone. I would request MongoDB to provide such a feature. Basically, I want a mobile version for both iOS and Android versions.

I have been using this solution for two years.

It is stable.

Currently, we have about 1,000 to 5,000 employees all over India. Most of us are using MongoDB for internal projects. 

When I was getting trained in the data engineering field, there was a saying that if we run after the technical support, we won't be able to see a bug in our own code. Since then, our superiors or colleagues don't suggest going for technical support. If anything goes wrong, we just troubleshoot it on our own, and we have done that successfully.

When we provide solutions for a customer, we look at the domain in which we are working, and accordingly, we recommend or select a database. It is up to the customers which database they want to use and how they are going to use it and leverage the subscription of that database. Do they want Oracle, MySQL, or SQL Server? Based on their preferences, we select the database.

For people or businesses that are currently trying to put their feet in the industry, it is a good thing to start their career with MongoDB. Sometimes, you don't have the knowledge of SQL and how to put a query to get a result. In MongoDB, there are certain things that make it different from other solutions. It is schemaless, and you don't have to have the knowledge of schemas. It is a good way to go ahead.

I would rate MongoDB a nine out of ten.

I have done a variety of things with MongoDB that started with the adoption of this solution at one company. I was involved in setting up the cluster and then the monitoring, alerting, and backup process. Once all of the set up was complete, I was involved in writing some of the components that were responsible for fetching data from MongoDB.

We are now responsible for running the platform, so whoever wants to run MongoDB comes to us and we explain how we can deploy the cluster for their applications. At this point, we build a cluster in the servers under a UNIX account. The number of nodes in the cluster depends on the requirements of the application side.

Some of the use cases we have configured MongoDB for are desk-tooling and a payment card profiling project. We are currently working on a data exchange platform. We also have a couple of use cases in the pipeline for potential MongoDB clients who also need the MongoDB Ops Manager.

The most valuable feature is that we don't need a schema to store the data.

The security is very good. Cybersecurity, authentication, authorization, and server certifications are all valuable features. We can define security rules at the database level or the cluster level to grant or deny access to particular users.

This is a highly available architecture. If you are using a three-node cluster and one of these goes down then either of the secondary nodes will become a priority to eliminate downtime from the application's perspective.

The documentation for MongoDB is not very good and should be improved. Some of the documents are referring to legacy versions. MongoDB 4.2 has been released, but there are training documents and other documentation that still refers to versions 3.6 and 3.4, which is not good. They should definitely update the documentation as new software is released.

Data encryption is possible using third-party tools but they should have their own encryption capability built-in to this solution.

Information about upcoming and recently released features should be made available so that we are aware of the latest features, and how we can manage the issues that will accompany them.

I have been working with MongoDB for the last three years.

We have not had any issues with stability.

We have a support portal where we can log tickets and fix issues. We contact them directly and we can set up a call whenever we need help from them.

For some issues, I would rate technical support a nine out of ten, or a ten out of ten. However, at other times, I would rate them a seven out of ten. It depends on who is dealing with the ticket. There are times where they respond to tickets very quickly and things get resolved in a timely manner. At other times, it takes ages to resolve the problem.

We did not use a different NoSQL solution prior to MongoDB.

We continue to use Microsoft SQL Server for other types of database implementations that require SQL, which I also have expertise in.

The initial setup is not very complex. We used the MongoDB resources to understand how to set it up on a Linux server, and after that, we prepared our own document that explains how to install it. Now it is quite straightforward, although if you are going with a more granular level of configuration, such as enabling other parameters on the cluster, then it would be different. I would say that set up would be a little more difficult, but not much. It's very simple using the MongoDB Ops Manager.

We offer three types of services on the MongoDB platform. First is the ODS service, second is the MongoDB SQL, and third is MongoDB standalone. For standalone, we are providing services on the tenant. With respect to shared services, we have the infrastructure but we have to set up their database on the shared servers. This will be useful for some use cases. The standalone configuration takes approximately 15 to 20 days to set up. It is sometimes less but it takes the time to create and configure the UNIX account because we have a third-party dependency for that.

The ODS solution will be better for enterprise data such as those involving payments, accounts, and customers. 

MongoDB is a solution that I can recommend because we have realized good benefits from it. We are in the process of setting up the ODS project, which should help the organization from a cost perspective. Then we will be moving the mainframe data to ODS, and we can use the MongoDB API to fetch data from there and provide real-time solutions to the customer.

At this time, I cannot judge the benefit of MongoDB in isolation, but as time goes on, perhaps by the end of the year, I will have a better idea.

I would rate this solution an eight out of ten.

If we don't have relational data we use MongoDB. It is in JSON format, and we can use JSON. Therefore, without relational data, without type coupling with columns, we can use MongoDB. We use it for queries.

The most important aspect is the clustering part. If you have read/write databases, then MongoDB will be easy to use. You can split those databases. We can save the data into JSON without relational data. 

It is very fast - faster than an SQL or MySQL Server.

Therefore, if you have unstructured data, you should go with MongoDB.

I work with Kafka. Kafka is sending a lot of data - millions of records in seconds. It is not easy to just pass it into the SQL Server. Instead, we are sending those drivers to the MongoDB Server, the MongoDB database. it is very fast

You can manage very fast queries with MongoDB in JSON format. 

The clustering is great. You can have multiple clusters in MongoDB.

It is scalable. Technical support is helpful. 

We'd like to have access to foreign keys.

Sometimes we need to be able to delete unintended data from the end user, and we'd like to have that capability.

The solution is a bit expensive.

There can be stability issues. 

I've been using the solution for three years. 

Sometimes you have multiple requests at the same time and there are thousands of millions of data points. There may be performance issues in that case. Sometimes it is stable and sometimes it is not. 

The solution can handle multiple clusters, so the scaling is fine. Sometimes scaling is not required if you have multiple read databases.

I also use AKS and you can use AKS functionality to scale MongoDB services. 

Technical support is okay.

Neutral

We have it deployed on the cloud with a container. 

It is not a complex setup. It is easy to use. You just compose a file and deploy it from there. 

We have one DevOps team that can handle deployment tasks there are three to five people on it.

We have not witnessed an ROI.

The pricing is okay. It's a bit expensive. I'd rate it eight out of ten in terms of affordability. 

We're using something around version three. 

Overall, I'd rate the solution nine out of ten. 

We do not use MongoDB extensively. Initially, we wanted to store login information, dumping the entire message into the database. It stores transaction details about the users, but only for login purposes. Essentially, we store information about access and usage.

In the future, we will build some reports for this data.

MongoDB is the best choice for us when we want to store NoSQL-type data.

The clustering is very good. It allows us to have high availability.

The performance is good. 

The user interface is not as friendly as Oracle, which is something that can be improved.

We have been working with MongoDB for a couple of years.

So far, MongoDB has been quite stable.

MongoDB is definitely scalable. By setting up a cluster, we are able to scale well.

At this point, we are only using it for login purposes and only with two or three applications.

We have not used technical support very much because we don't have any issues with it. It has been quite stable and also, we are only using it for a limited purpose at this point. 

We also use Oracle and we have found that if you want to have a DR site, you need to replicate the data from one site to the other. With MongoDB, we set up a cluster on the wide-area network, and we don't have to do any data replication. Instead, it will help you with these things.

With Oracle, the user interface makes it easy to explore the database. With MongoDB, the interface is quite primitive and it is more difficult to look at the data. It is not as user-friendly.

There are a lot of vendor and third-party tools that work on top of Oracle, but this is not so much the case with MongoDB.

I was not personally involved in the installation.

We have an in-house team for deployment and maintenance.

We did not evaluate other similar solutions before implementing MongoDB.

Prior to MongoDB, we focused on relational databases.

This is a good product and I recommend it for anybody who wants to store NoSQL data. It provides a lot of features and the clustering, in particular, is a good one.

I would rate this solution an eight out of ten.

We primarily use the solution for web applications.

It has quite good web analytics. It is pretty stable. There is more in-depth management of the data.

It's a NoSQL/Document DB and has some peculiarity related to the data schema but it's also good as a general-purpose DB.

The replication works very well and is in the box. 

In clusters, there is the choice to have horizontal scaling, which improves performance on a huge amount of data.

The aggregation framework is very powerful when elaborating on data. 

It has good high availability.

It's an essential DB. 

It has very good performance for queries.

It is free to use if you choose the community version.

It is stable and reliable.

You can easily scale the solution.

It's quite a good DB that is very strong on a lot of features. 

It is a product that works very well. I don't see a lot of areas that need improvement. 

I've used the solution for five to six years. I've used it for a while now. 

I'd rate the stability nine or ten out of ten. There are no bugs or glitches. It doesn't crash or freeze.

I'd rate the scalability nine or ten out of ten. It allows for horizontal scaling, which is quite useful when dealing with big data.

We have about ten people using the solution at this time. One-third of the company ends up using the solution.

We may increase usage. It depends on the business needs. However, in Italy, I have noted MongoDB is expanding.

The technical support is very good but is available only for the enterprise version. 

When I've used other DBs I found them to be inferior.

We have used also Atlas (MongoDB solution for Cloud), and MongoDB has developed a useful framework with lots of new features that are not included in MongoDB's on-premise version. If you choose a cloud DB, it's great if you are looking for a lot of innovative features. 

Many clients use SQL DBs and many are moving over to MongoDB.

The initial setup was pretty straightforward to set up. Compared to other SQL DBs, SQL databases are very complex. MongoDB is ready to go, and you need less operational knowledge. 

I do not invest in MongoDB. However, many customers can save money by leveraging the MongoDB community version. 

The community version is free. The enterprise version is reasonable as MongoDB wants to expand and outpace also SQL DBs. 

I am not using the latest version of the solution. 

Do not think of this solution as a SQL database. Consider your use case and set it up accordingly.

I'd rate the solution ten out of ten. It's the best database on the market.

We use it in our virtual environment.

Our software produces a lot of predefined JSON Structures. We save those JSONs in an encrypted form inside MongoDB.

It's simple storage of JSON. We do not perform any database functions.

In our case, it is most important to have redundancy. It supports a replica set and it allows us to use mutual TLS for authentications with the certificates.

The documentation is useful.

We work with the community edition and it would be really nice to have for the database side encryption, but it's not available in the community. It is only available in the enterprise edition.

We use mutual TLS, which means we use the certificate for authentication and connection encryption.

When I want to connect to a node, I need to supply the certificate that MongoDB trusts, even though I use an admin password. This is not useful, and it complicates things.

It would be much more useful if I have an admin user and a password.

I would like it to be more straightforward when connecting to a node.

We have been using MongoDB for the last 12 months.

We are using version 4.4.0.

It's pretty stable. We don't have any complaints.

It's a scalable solution. We haven't had any issues. 

We are in development mode, and not really used by users. We have five people for development.

We can't know for sure if we will continue to use this solution. We are still in the development phase so we have to see when we finish.

I have not contacted technical support. I used the official documentation, which was enough for me.

The initial setup was straightforward. We used Docker, so it was pretty easy.

It didn't take long to deploy.

It's free. It's a community edition, so we do not pay anything.

There are no additional costs.

We didn't really evaluate other solutions. We did not have strict requirements in choosing a database. We just needed to keep JSON files informed when we produce them and MongoDB seems to be fine for us.

I would rate MongoDB a nine out of ten.