MongoDB Reviews

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.

I use MongoDB whenever I want to use non-relational data. I use the solution to make a non-relational database or objected data for my personal project related to social media. MongoDB stores the JSON data, and it's easy for me to understand because I'm a JavaScript Developer.

MongoDB should improve its data loading part. If I update data with MongoDB via the browser, the loading takes a lot of time when I want to use the updated data. The loading is further slowed down if my internet is slow. We use MongoDB Compass to avoid these types of issues.

I have been using MongoDB for four years.

MongoDB is a stable solution, and I haven’t seen any bugs in it.

I always connect the solution using the same method. I recently tried to connect to MongoDB, but I couldn't do so. I contacted the technical support team, and they told us that our server is an Asian server. They told us the issue would be fixed automatically in two or three hours. I waited for the server to be fixed and then resumed work. I did not directly contact the support team. I asked another developer facing the same problem to contact the support team.

The initial setup of the solution is easy for me, but it's not easy for any beginner to learn MongoDB. MongoDB gives us the connection string that I connect to the node to ensure the connection is done. MongoDB sometimes gives us an IP problem if their IP and my IP are not the same. MongoDB uses a private IP, but I can use a global IPL.

Sometimes, beginners can't understand why the database is not working despite them connecting MongoDB the way I showed them. Sometimes, my junior developer comes to me and asks why the database is not working. By default, MongoDB sets a strict IP address. Then, I edit the solution's private IP and change it to our global IP. Using a MongoDB connection string is a bit hard for a beginner, but it gets easier as they practice it two or three times.

MongoDB is a non-relational database that is deployed on the AWS and Azure cloud. I recommend PostgreSQL or MySQL to users who do not want to store data in JSON format. I also recommend MongoDB to users who want to build a project that stores JSON-type data in the database. MongoDB makes it easy for me to read the data from a JSON perspective and fetch the data from the database.

Connecting to MongoDB will be easy if you learn the queries and how they connect or manipulate data. For the first time, you have to learn the solution's queries and data flow to use it. The learning process for MongoDB is easy because it has easy-to-understand documentation. Any beginner can read the documentation and try to use the solution.

Overall, I rate the solution a nine out of ten.

We installed MongoDB on an EC2 instance and used it. 

Use used MongoDB for a NoSQL use case.

The most valuable feature of MongoDB is the ease of connections, aggregation, and queries. Additionally, there is plenty of documentation available for assistance if you require it.

MongoDB should incorporate more features, particularly search functionality, and real-time communication capabilities, to improve the database and provide data listening services. Currently, we rely on the Atlas offering, but it would be fantastic if MongoDB could develop a new solution or updated version that includes these features within its internal database and driver. However, I am uncertain if this would be a viable or profitable move for them, and I am speaking from a mobile-centric viewpoint.

I have been using MongoDB for approximately six months.

The solution is stable. However, I recall instances when the database crashed due to high-volume querying, but this can occur with any database if the queries being run are not optimized for the particular instance.

I rate the stability of MongoDB an eight out of ten.

I rate the scalability of MongoDB a seven out of ten.

We were using PostgreSQL for everything, but it is not the best fit for our needs due to the diverse nature of our data. We switched to MongoDB, as NoSQL is better suited for this scenario.

I have received a return on investment using MongoDB.

The pricing is favorable if you opt to install MongoDB on an Amazon EC2 instance as you won't have to pay for the extra Atlas services and can instead manage the scaling yourself. This allows for a cost-effective solution and using MongoDB on a small scale, I have been able to utilize it for free.

I rate the price of MongoDB an eight out of ten.

I rate MongoDB an eight out of ten.

I primarily use MongoDB for personal projects or minor stuff that I have developed for people who are starting. I'm currently doing testing on MongoDB for new features we're developing at my company.

It's super easy to develop a couple of solutions for clients with MongoDB, like a quick web page with no clear data structure that they need to spin up quickly to validate some sort of MDTP.

The MongoDB documentation can be a little complicated sometimes.

I have used MongoDB for three or four years. 

MongoDB is solidly stable. 

I rate MongoDB nine out of 10 for scalability.

I rate MongoDB support nine out of 10. It's pretty good.

Positive

Setting up MongoDB is super easy.

I rate MongoDB nine out of 10. I recommend reading up on NoSQL in general to learn the best practices. 

Sharding is an excellent feature of MongoDB. Atlas is an awesome feature of MongoDB that makes life easy.

People coming from RDBMS should have the flexibility to write queries in SQL that can be converted into JSON queries. This feature is working, but we can still achieve some integration and make it more flexible. It is not as easy as writing direct queries on Atlas. This feature will definitely increase a lot of users. RDBMS users think this is a different query language, MQL, which is uncomfortable for them.

I have been using MongoDB version 6.0 for more than 12 years as a customer.

MongoDB is a very stable solution. The solution is a leader, according to the Gartner report.

In our company, around 2000 to 3000 people are using the solution.

MongoDB’s technical support is awesome.

Positive

We previously used the RDBMS solution, MySQL.

MongoDB has five to ten times better performance than MySQL. MongoDB has a lot of advantages. With MongoDB, you can store any kind of data, including structured, unstructured, and semi-structured data. MongoDB has a lot of benefits over RDBMS.

It is very easy to deploy MongoDB. If it is deployed on-premises, it takes an hour. It does not need any additional prerequisites or configuration details.

We have seen a lot of ROI with MongoDB because it gives five to ten times better performance.

MongoDB's pricing is not reasonable, but it is not as expensive as the others.

The solution's pricing depends on the deal, which includes how long you will use it and the number of deployments. They do not have a fixed cost. However, the maintenance and support cost is included.

I am satisfied with the product.

Our organization has a DBA team of 50 people. However, the work for the DBAs is minimal because MongoDB intends to have zero DBA. They want to develop a product where the need for DBAs is minimized.

Users should approach MongoDB with an open mind, without thinking that it's a different technology altogether and has a different language. Users don't need to develop the application based on a schema. They can develop the application, and the schema will follow.

Overall, I rate MongoDB an eight out of ten.

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 use MongoDB mainly on the back end. We use it in my company for the database, and I also use it on my side projects.

MongoDB is a NoSQL tool that gives us much freedom to manipulate how the data works.

MongoDB should support TypeScript.

I have been using MongoDB for about two years.

I haven't had any issues with the solution's stability. However, our company faced an issue where the tool was down for two hours.

I rate the solution’s stability an eight out of ten.

MongoDB is a very scalable solution. About 10,000 users are using the solution in our organization.

I would recommend the solution to other users because it's scalable and easy to learn. The solution's documentation can be rigid and hard to understand initially. Users should use an ORM or ODM. They should use Prisma or Mongoose as the starting point for using MongoDB. MongoDB is easier to manipulate. The easier the onboarding, the harder the maintenance.

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

The primary use case is data retrieval. It allows for easy retrieval of data as all the required information is stored within the document. This becomes particularly useful as the company scales, preventing queries from becoming sluggish.

Working with it extends beyond database skills. Utilizing additional tools such as ML frameworks (e.g., TensorFlow), languages like Python for data analysis, and platforms like Apache Spark for distributed computing can enhance one's capabilities in extracting meaningful insights from data.

It facilitates the generation of heatmaps for graphical data analysis. This can be valuable for visualizing patterns and trends in data. While other databases like Cassandra may also serve this purpose, MongoDB stands out for its simplicity in handling complex queries and graphical data representation.

It has certain limitations when it comes to handling hierarchical data, enforcing relationships, and performing complex joins, which should be taken into account when designing databases for applications with intricate data requirements.

I have been working with it for a year now.

It is highly stable. I would rate it nine out of ten.

It emerges as a favorable choice for customers seeking efficient data storage and scalability. On a scale of one to ten, I would rate it at eight.

I have been working with both MongoDB and HIVE and the choice between them depends on the specific requirements of the client. While I've been actively engaged with both databases, the preference depends on the nature of the data and whether file storage is required. If data retrieval is the primary focus without the need for file storage, I opt for MongoDB. On the other hand, if the client requires storage for both data and files, HIVE becomes the main choice.

I would rate the initial setup six out of ten.

I only used the open-source version.

Opting for MongoDB could be beneficial, especially for storing large volumes of records, even for transient data. The decision hinges on the nature of the data itself. If there is a significant amount of metadata, it becomes a preferable choice for its scalability and superior query performance. It's important to anticipate future operations; for example, if there's a current load of ten thousand audio and video files, MongoDB can efficiently handle it. Overall, I wold rate it eight out of ten.