MongoDB Enterprise Advanced Reviews

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.

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 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.

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.

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.

Our main purpose is to build a historical data lake containing commercial data of service usage, products, retailers and wholesalers, AAA sessions, account recharges and transferences, et cetera. We're looking at the whole company's key internet usage data from a commercial perspective. 

The data lake holds data from 5 years, so now we're triggering ML processes. The impact of the product in the community has been huge, and by that I mean, the community of developers that make apps for the telecommunications market. 

In our country, we were pioneers at using MongoDB. Now, at least 7 developer teams are using it.

It fits well. Data we want to keep represents facts. We've ETL'd from operational systems, so there was no need for relational engines. MongoDB allows us, through replication and sharing, to build a robust platform for keeping data. Even when volume starts to be an issue it is really easy to escalate horizontally and connectors do the rest. 

I thought that choosing javascript as the internal query language might be a mistake, but that was a very good choice. 

The fact is all of our users are happy with the stability and quick response times our solutions have. All of them are based on MongoDB as a persistence engine.

MongoDB is very stable, and, by that I mean, amazingly stable. Using javascript was the key to have a wide range of functionalities based on its syntax and grammar. The aggregation framework is really good, allowing a developer to build very complex queries. The fact a developer builds some functions and can run through the whole cluster, actually and efficiently using all the resources available, is a great advantage. It's given the developers a very robust path to building whatever procedures they need. MongoDB is very, very stable.

The product roadmap shows us that the MongoDB team is very professional. Since we started using the product, it's like having wizards that are one step ahead of our needs. They are looking at the community, the market, and the competition. 

From my point of view, they need a totally free IDE to work at high levels. The best I know is Studio3T, but licensing and an embargo in our country make it difficult to access. MongoDB needs something like Studio3T (Compass is just fine, but it isn't Studio3T) to really get the whole developer community.

I've used the solution for more than six years.

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.