MongoDB Reviews

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.

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.

We use this solution for database verification purposes. Typically, we integrate other analytics tools with the solution, like databases and other tools.

The Dynamic Application is a valuable feature.

The analytics needs improvement.

I have been using MongoDB for a couple of years. 

Hundreds of users use the solution at present. 

The initial setup is straightforward.

Overall, I would rate the solution an eight out of ten. 

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.

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. 

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.