MongoDB Enterprise Advanced Reviews

We recently had customers asking about MongoDB, so we have started to deploy new environments for that. We have implemented it may be four times. We are implementing it for our customers in our own infrastructure. We have done on-premises as well as cloud deployments. 

Our database team works on the use cases. I work only on the implementation part. I am responsible for getting the clusters up and running. I'm just managing the server and guaranteeing that the clusters are up and running and backing up. I also handle the monitoring.

It is very easy to create a MongoDB cluster. You can deploy three nodes in one hour.

You can do small configurations to enable routing. It is easy to implement.

It should have GUI for managing clusters. MongoDB needs a more powerful GUI to manage clusters and make switchovers. Currently, there is no good, free tool to check the replication to find out if there is a gap. 

It is very stable.

It is very scalable. You can add nodes every day to the replica.

I have no experience with technical support.

It is easy to implement. One person can manage ten managed MongoDB clusters.

At the moment, all customers are using the community version.

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

We use both SQL and MongoDB and they have similar characteristics. We use both tools for our work. We have less than 50 users on MongoDB in our organization.

Its flexibility, and cost. It is reasonably priced.

MongoDB should be more stable, and support should be more efficient.

We have been using the latest version for the last two years.

We have some challenges but we are working on them. It should be a bit more stable.

It is scalable.

We have some challenges with support, but we can usually get the right people. Customer support could be more knowledgeable, customer-friendly, and faster.

MongoDB is not a difficult product to setup.

We do not need a big team for deployment, or a high level of technical expertise. We have a couple of managers and admins.

We did not consider another product, as MongoDB was part of the whole implementation.

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

We use this solution to store log files. We have a Cloud telephone product and we use MongoDB to store our calling records. A number of users have access to it. 

We plan to continue using this solution.

MongoDB is relatively fast compared to relational databases. The files are stored in XML format, which is a stable format. 

MongoDB is also great for managing logs.

Databases provide the data and any software can access those databases as per the access protocol — the database itself provides the data.

You can have the same database in multiple geographic locations. You can update it from different locations and the other locations also get updated. In that way, it is a good product. Very good.

You can update the server from another platform (Mongoose) which sits on top of MongoDB and makes it a relational database. The beautiful thing about MongoDB is that it's not a relational database — multiple statements are there so it's easy to access. It serves the purpose for which we are using it.

I suppose it could be a little more secure.

I have been using this solution for a couple of years.

This solution is both scalable and stable.

We are actually using the community version so we manage it ourselves. We have engaged a consultant so if we have any problems, we just sort it out with him.

We were also using MariaDB, but MongoDB is good for certain situations in which MariaDB is not suited for. For example, managing the database of log files is easier with MongoDB.

You don't need many people to install MongoDB or to fine-tune it. You need a database expert if you have any problems, but it is fairly simple.

I didn't install it. I believe my team had to spend some time learning how to handle MongoDB, so they gained some expertise and they started using it. Overall, installation doesn't take longer than one hour.

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.

We use it for document storage and testing of a proof of concept.

I like the document storage feature. It's pretty simple. I also like the distribution of databases. It's easier to put information about my users.

It would help if MongoDB offered a light solution for small projects. Its become a very big database, and we need a smaller solution for our end-users.

I have been using MongoDB for two years.

MongoDB is stable. It's a good server. If you install perfect hardware tools and follow best practices, it'll be a good solution.

MongoDB is scalable. It's very good.

The initial setup is straightforward. It isn't hard to set up, make a cluster, and distribute.

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.

We use it just for data storage. I joined this company two months ago, and I am just testing it on my local machine. I haven't used it a lot.

It is easy to set up.

It would be good to have scalability for clusters. For example, if we have three clusters, we should be able to increase to five clusters if required. I am not sure if such a feature is currently there. I hope there is good documentation for this.

I have been using this solution for half a year.

We're just doing something new, and we are still in the testing stages. Based on our experience so far, it is stable.

It is scalable.

I haven't contacted their technical support.

It is easy to set up.

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

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.

We primarily use the solution as a database. It's basically used as a storage engine.

The solution is a very dynamic product. It becomes extremely easy for us to support user requirements and we also make use of the simplicity of a cloud redeployment.

The solution is easy to deploy.

The product can scale quite well.

The cloud version of the solution is very affordable.

The solution's most important aspect is its seamless database.

The solution offers excellent documentation.

The on-premises version of the solution is still pretty expensive, especially compared to the cloud version.

The management on the cloud is pretty good, however, the on-premises deployment model is a bit more difficult in this area.

If they want to make their product a little competitive, they'll have to go to organizations and get a bit more commercial in their approach. They need to think about pricing and licensing for RDBMS players. For them to be competitive in the market, they will have to think of strategies other than what they have currently. Their pricing definitely needs to improve.

We've been working with the solution for four years now. It's actually coming up on five years soon.

We've never faced any issues with stability. It's been very good so far. It doesn't crash or freeze, and it's not buggy by any means.

The solution is extremely scalable When we need to expand it out, we know we can do so easily.

We have about five products that factor into the needs of the BFSI segment in India. These proprietary products developed on five or ten platforms. We don't develop MongoDB, we just use it as a storage platform.

Currently, we also use RDBMS. We use Oracle for some other products. We don't just use MongoDB exclusively.

While Oracle is better for transactional services, MongoDB is extremely good at support services. That's the main difference. I have seen people use MongoDB for transactional as well, however, I have never attempted it, so I can't speak to it's capabilities.

The solution is very easy to deploy. The implementation is not complex at all.

The on-premise implementation takes a bit longer. We're looking at a six month implementation for one of our clients, for example.

We handle the implementation ourselves in-house. We don't need the assistance of a consultant or integrator.

For people who can afford it, there are good subscription offers that are available on the cloud as well as on-premises. On-premises is still a little expensive. However, if a company decides to go to the cloud, it is pretty affordable.

If the company is small, there is a community edition that can be taken advantage of. If a company needs to scale quite a bit, they'll need to move up to the enterprise version.

Due to the fact that we are a BFSI focused product company, we typically recommend that users go for the enterprise-level license.

There is also pricing surrounding support. We're in discussions with MongoDB about that now. I don't know the exact costing just yet, however, I know it isn't free.

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.

We use MongoDB in different products. The first is a Business Process Management System (BPMS) that we have developed for ourselves. MongoDB stores all of the data for business flow management.

The second product is in the capital market. We have implemented it to use all of the stock-related data.

We have also developed an online shipping product, using MongoDB for storing product features.

The most valuable feature is that you can store unstructured data, which is helpful when you don't know what the best structure should be and you cannot use a relational database because of that. For example, in our online shopping product, different products have different features and there is no structure for all of the data.

The usability is good.

Compared to a relational database, the performance is good.

The performance can be improved. While it is good compared to relational-type databases, it could still be improved.

Stability-wise, there is some room for improvement.

I have been working with MongoDB for between four and five years.

If you take care of the application and check everything then it will be stable. However, if you do not maintain it properly and do not have support then stability will be a problem.

We have not tried to scale our implementation of MongoDB.

We do not have direct support for this product. Instead, we have used the community-based resources that are available on the internet. For example, we have searched for questions and taken advice from the community in order to resolve our problems.

We may have used InfluxDB for some reason but I don't recall any of the details.

The initial setup is simple and not a problem to complete. I don't recall the exact length of time that it took to deploy, but I think that it was completed within one or two days.

We deployed MongoDB ourselves.

We have two administrators who maintain and work with it on a daily basis.

We use the open-source version, which is available to use free of charge.

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.

We are a solution provider and we develop applications.

Our primary use of MongoDB is data analytics and it is also used for document management.

MongoDB has a simple data-loading interface. It is not as formal as a traditional database system.

There should be better integration with other databases.

The security should be improved.

We have been working with MongoDB for two or three years.

We have had no issues in terms of stability.

This is a scalable solution that is better for data analysts when compared to a traditional database.

I have used other databases but they were SQL solutions. MongoDB is different because it is a NoSQL solution and the structuring of data is less formal. It has to be formatted internally.

The initial setup is good.

This is an open-source solution.

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 using this solution for storage and mapping. We have developed an application for mapping. We source the GeoJSON position for approximately eleven million points.

Our application is made for desktops, and we started using MongoDB for that application.

We have four teams in our laboratory and the other teams are developing their applications to be used with MongoDB.

The primary use of MongoDB is for mapping the application.

The most valuable feature is the geometric information done with GeoJSON. We search the points, and we can perform searches for the data using the RPA for MongoDB. We can ask for points in the geometric shapes or points near other points.

Simplifying the aggregation framework would be an improvement.

Also, the replica system could be improved.

I have been using MongoDB for approximately four years.

We have anywhere from 15 to 20 people using this solution on a daily basis.

This is a stable solution and we are happy with it.

It is possible to scale this solution but it has a problem with the replication.

I have not contacted technical support. We have been able to resolve any issues we have had on our own.

Previously we used MariaDB and we continue to use MariaDB for other purposes. We started using MongoDB to manage non-relational data.

The initial setup was simple and straightforward.

It took a couple of hours.

I am the only one maintaining this solution.

I completed the initial setup and implementation.

I did not use the help of a vendor or integration. I did it on my own.

MongoDB is an open-source solution.

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.