What advice do you have for others considering MongoDB?

To start with MongoDB, I recommend reading their documentation, as it is quite sufficient. I'd rate the solution nine out of ten.

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.

We are currently using the on-premises version of MongoDB, but we are moving to the cloud. I would recommend the solution to other users. Overall, I rate MongoDB an eight out of ten.

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.

The NoSQL structure, particularly the document-based data management, has made data management easier for me. MongoDB's approach to handling data in documents rather than traditional tables has been particularly beneficial. MongoDB's document-oriented model improves development speed by providing each document with its built-in key or ID, similar to a primary key in relational databases. This inherent ID facilitates faster execution of operations, such as searching for specific documents. Additionally, it allows for creating additional indexes, further enhancing performance. The familiarity of JSON-like structure makes it easy for developers, both front-end and back-end, to work with, leading to quicker development and visualization of data. I advise others to understand the fundamentals of databases and how they store data. They should start with online videos to grasp the ecosystem, focusing on concepts like data storage. The document-oriented structure with binary objects is crucial for individuals with a programming background. Several limitations related to querying certain documents can be challenging. They express concerns about the lookup process, where we sometimes need to fetch a large amount of data simultaneously. Additionally, there are limitations regarding the size of documents, which may require restructuring or storing data. I rate it an eight out of ten.

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

I rate MongoDB a nine out of ten.

The integration capabilities of MongoDB are fine for the solutions that we use in our company. The tool's vendor takes care of the product's maintenance. I rate the overall solution an eight out of ten.

I advise others to evaluate a lot of other databases. MongoDB worked fine for my project. However, I would have selected a product besides MongoDB to improve my skills and learn something new. I rate it a six out of ten.

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.

I rate the solution a six out of ten.

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.

MongoDB is a fast and safe solution. I would rate this solution as a whole a seven, on a scale from one to 10, with one being the worst and 10 being the best.

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

I give the solution a seven out of ten. Three people are required for solution maintenance. We chose MongoDB because of the speed. MongoDB is a good solution and I recommend it to others.

I really like the solution and rate it a nine out of ten.

Only one person is required for the maintenance of the solution. I recommend MongoDB to others. I rate MongoDB a nine out of ten.

I would recommend this solution to others. I rate MongoDB a six out of ten.

I'll give MongoDB a 10 out of 10. We are getting positive feedback, so far.

I would recommend this solution to others. I rate MongoDB an eight out of ten.

Depending on your project, I would recommend MongoDB. On a scale of one to ten, because it's free, I'd give MongoDB a 10.

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.

As we have not finished our evaluation yet, I can only give it a rating of seven out of ten. I can't recommend it yet for the same reason.

Going by my level of experience in these solutions I would recommend it to others. I rate MongoDB an eight out of ten.

I would rate MongoDB a nine out of ten.

I would rate MongoDB a nine out of ten.

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 customers and end-users. We are likely on the latest version right now. You can adopt this tech very easily on your private cloud. AWS is actually broadly supporting and it's not only us but also a lot of other industries. MongoDB is not unknown. There are a lot of people that have experience with it, however, it's very important if you have a company that is evaluating something, to have the ability to execute. If you have some local vendors, if you have international vendors, if you have some integrators that are able to use it and to help you use it, MongoDB is a good choice. I'd rate the solution five out of ten.

I would recommend this solution to others. Having the solution in the cloud was a very clean process. I rate MongoDB a nine out of ten.

I rate this solution seven out of 10.

I'll recommend MongoDB to potential users any day. On a scale from one to ten, I would give MongoDB a nine.

I would recommend this solution to others who are considering using it. I would rate MongoDB a seven out of ten.

We have the solution deployed both on-premises and on the cloud. We're using the latest version of the solution. I'd recommend this solution to others who are curious about using it. In general, I would rate the solution at an eight out of ten. It's been pretty good overall and we're mostly satisfied with its capabilities.

I rate MongoDB a nine out of ten. If I put it this way: "Can I trust this technology to perform well in a complex project?," I can certainly trust MongoDB. I have been working with some graph databases as well, and MongoDB was my first touch with noSQL technology. I think I like it even more now, after these experiences I had. I use MongoDB from a development point of view. For some projects, we use Docker on local environments. MongoDB actually starts in some Docker microservices where we don't run the whole platform, we're actually running locally or maybe part of the platform. With this container, we don't need to do many things with the image in Docker, we're just developing the platform. And then the deployment and scale are managed by the DevOps guys, who do their magic. We use Azure in some projects, but we mostly use AWS.

I would recommend this solution to others. I rate MongoDB a nine out of ten.

I developed an application using the solution. We made many improvements to the solution. I do not have the requisite experience to properly comment on the solution's security and stability. There are around 200-plus users making use of the solution in my organization. We are talking about a rapid activity and replication solution which serves our needs well. I recommended it at the time. I rate MongoDB as an eight out of ten.

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.

This is a product that I can recommend to others. I would rate MongoDB a nine out of ten.

I would recommend MongoDB to others. It is good in terms of support. I would rate MongoDB an eight out of 10.

I would tell potential users to just try it out. I would recommend this solution to new users. On a scale from one to ten, I would give MongoDB an eight.

It's a very good product, and I would rate it at nine on a scale from one to ten.

While I may advise clients on MongoDB, I don't have a direct business relationship with the company. We always use the latest version that is available. As we implement the solution for clients, we deal with different deployment models. Typically, for banks, for example, the on-premises deployment is used. However, we've looked into the cloud as well and some clients may consider that deployment instead. A company considering the solution needs to first think about the project and the infrastructure that they need to implement. Every solution is different. I cannot say that I feel some particular way about MongoDB. It always depends on the organizational need. I'd rate the solution at a seven out of ten. I'd rate it higher if it offered more upfront support and a lighter solution for smaller organizations. It would be great if they could build an open-source version, for example.

I would highly recommend this solution. I would rate MongoDB a nine out of ten.

At this point, I rate MongoDB a 6 out of 10. We are going to keep using MongoDB.

I would absolutely recommend this solution to others. Overall, on a scale from one to ten, I would give this solution a rating of eight.

I would recommend it to potential users who have a big project because MongoDB is good for big projects. On a scale from one to ten, I would give MongoDB a nine.

I would rate MongoDB an eight out of ten. It is a good product, but it requires some improvements.

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.

It is a good tool. You should give it a try. It has a very good and different perspective of looking at how data can be stored in a database and restored from a database because it is not like a straight query or record. The data is just in files. It does whatever a database should do. I would rate MongoDB a nine out of ten.

We are a customer of MongoDB. We don't embed it in our application, however, we recommend it to our clients who use our product. We're mostly on the cloud deployment version of the solution However, we do have a banking client who requires an on-premises solution. We work with both and have experience with both. This solution is perfectly suited for companies of all sizes, from small to large. Small companies can definitely use the community version, however, this product offers an enterprise-level license for much larger organizations as well. I'd advise new users to be flexible and be able to change their mindset when it comes to MongoDB and what is in the RDBMS. there's a bit to unlearn before you re-learn MongoDB. The solution does have a good survey of languages and it's quite good. Due to the fact that is scales well, I'd rate it eight out of ten.

My advice for anybody who is considering MongoDB is that when we want to have flexibility in storing our data, I recommend using it. We can store anything, in any format, in any size, and accessing the data is the same speed. In the case where you have structured data or it is in a unique format, this is not the product that you use. In summary, this is a good product and it has been very useful for our purpose. I would rate this solution a seven out of ten.

Most of the features are very nice and MongoDB is a solution that I would recommend. If a company or organization needs a document management platform or is doing marketing analysis then this is a good product. I would rate this solution a seven out of ten.

We are a small laboratory and always look for open source solutions or solutions where the licensing is every year. We are prepared to do the troubleshooting ourselves. The most important part is to evaluate the rest of the ecosystem integrations. When we started, the driver that we used to develop the application was in C++ wasn't relevant. At the start of the project, we had some difficulties because there was no documentation available. There were no examples and no support from the community. You have to take into account the languages that you are using. If you are going to develop in the main languages of the solution such as Python, or JavaScript, then you won't have to worry. I would rate this solution a nine out of ten.

I will rate this solution a seven out of ten because I like the interface and the integration with other tools. In the next version, perhaps they can modernize the storage options. I think they have a very good reputation, from what I hear from our client comments. The program has speed and it has simplicity. If you want to extract the application, the terms of applicability it is good. And you can use the intelligence within the program.

The features that I have looked for are in this solution and we are using an older version. The current cloud-offering, MongoDB Atlas, has even more features. It would be a natural fit for us, but it will not be easy to move because we have a lot of dependencies. We have to update drivers, isolate collections, and take care of other issues before we can switch. My advice for anybody who is implementing this solution, or any other database, is to take care to plan your indexes because it is extremely important. Spending some time designing the document structure in the initial phase will certainly help you in the long run. I would also suggest that in terms of sharding, try to think about it as early as possible so that when you are ready to scale, it will certainly help to reduce the workload. Do not rely on MongoDB for any of the analytics use cases. Aggregation works well but do not use it for your reporting or analytics or number crunching-related tasks. I would rate this solution a nine out of ten.

I would rate the rate the solution as a seven (out of 10).

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.

MongoDB Atlas was the deployment mechanism we went with and that was hugely helpful for us. MongoDB Atlas is part of the MongoDB suite, I think. It's just a deployment of the Mongo. We also deployed it on Amazon using DocumentDB, but we found that MongoDB Atlas worked better in the end.

My advice is not to use Relationships in MongoDB. MongoDB is not a relational database, so don't try to use Relationships in MongoDB. I would rate MongoDB as eight out of ten.

My advice to others would be not to use MongoDB for complex business applications or difficult queries. There are some integration issues that need to improve, so I will rate this solution an eight out of ten. Still, it is a very good product that is user-friendly and it works fast.

The solution scales very well and is very easy to replicate. If you need something done quickly and you need something that does scale fairly well I would suggest MongoDB. You can always transition away from it later on. It's always a solid first bet if you want a simpler kind of web page or web system. It's a very solid choice if you want to get up and running quickly. It's my go-to for all these little startups that I manage. MongoDB seems to give just exactly what we need and I find most of my clients have never transitioned away from MongoDB. I would rate the solution seven out of ten.