MongoDB Enterprise Advanced Reviews

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.

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. 

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.

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.

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 are using MongoDB for unstructured databases.

The most valuable features of MongoDB are we have a lot of documentation and SQL-based applications that run on it.

MongoDB could improve by not having so many updates and different versions.

I have been using MongoDB for approximately two years.

MongoDB is stable, but there are always a lot of patches and upgrades every now and then.

MongoDB can scale but you will need to pay for the upgraded solution.

I have not contacted the technical support of MongoDB.

The initial setup of MongoDB is simple and the implementation took approximately one day.

We did the implementation in-house.

MongoDB is a free solution. We wanted to have high availability and the subscription cost was quite expensive because the basic one is free and then when you want to have some other replications or other features you will need to pay money. Overall the solution is expensive.

I would recommend this solution to others.

I rate MongoDB a six out of ten.

We use MongoDB for the applications. You can save two or three applications but there's a lot of people using those applications. 

MongoDB is cool. There is a difference between relational databases and newer databases like MongoDB. MongoDB is scalable and fast.

It could be much more flexible like SequoiaDB. I would like to see more flexibility in the next release, especially when working with Microsoft Windows. A lot of people struggle with MongoDB because of their Windows versions. But Linux is faultless and mostly runs nicely.

I have been using MongoDB for about five years.

MongoDB is a stable solution.

MongoDB is a scalable solution.

Customer service depends on your subscription. Suppose it's open-source, then hard luck because you won't get any support. But if you are paying for it, you can get some tech support. However, MongoDB's open-source community is also quite helpful. I'm satisfied with it.

The initial setup is straightforward. 

We implemented this solution by ourselves. One engineer is enough to deploy and maintain this solution.

You only have to pay for the paid version, not the open-source version.

I'll recommend MongoDB to potential users any day.

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

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.

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.