We changed our name from IT Central Station: Here's why

MongoDB OverviewUNIXBusinessApplication

MongoDB is #1 ranked solution in top NoSQL Databases. PeerSpot users give MongoDB an average rating of 8 out of 10. MongoDB is most commonly compared to InfluxDB: MongoDB vs InfluxDB. The top industry researching this solution are professionals from a comms service provider, accounting for 26% of all views.
What is MongoDB?
Open source database alternative to relational databases. It simplifies development and is extremely scalable.
MongoDB Buyer's Guide

Download the MongoDB Buyer's Guide including reviews and more. Updated: January 2022

MongoDB Customers
Facebook, MetLife, City of Chicago, Expedia, eBay, Google
MongoDB Video

MongoDB Pricing Advice

What users are saying about MongoDB pricing:
  • "We are using the Community Edition of MongoDB."
  • "MongoDB has a free version. You can also buy the enterprise edition, which is cheaper than Oracle."
  • "We use the open-source version, which is available to use free of charge."
  • "It is rather expensive."
  • MongoDB Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    Pranesh Vittal
    Associate Director - Database & DevOps at Medlife
    Real User
    Top 5
    A flexible solution that is cost-effective and developer-friendly
    Pros and Cons
    • "MongoDB is extremely developer-friendly because when you are starting, there is very little time needed upfront in terms of planning."
    • "MongoDB should not be used for reporting, analytics, or number-crunching tasks."

    What is our primary use case?

    When the company started, MongoDB was our primary database.

    It offers great flexibility where developers can define any key and assign a value to it. This means that there is very little that one has to plan in terms of designing the schema upfront, so developers enjoy a lot of flexibility. Now that we have more use cases for which NoSQL is not suitable, we are trying to move those workloads out of MongoDB.

    What is most valuable?

    MongoDB is extremely developer-friendly because when you are starting, there is very little time needed upfront in terms of planning. Whenever a developer wants to build a certain feature, they simply define a key and a value and that's it.

    It is very easy to create an index on a field that you want to have searchable.

    All of the documents are stored in JSON format, which gives developers a lot of flexibility.

    What needs improvement?

    MongoDB should not be used for reporting, analytics, or number-crunching tasks.

    The pricing should be improved because the whole design is around replication of data, so in terms of storage costs, in the long run, it will be expensive. The amount of storage grows very quickly when compared to other databases that store data in normalized form. If there were a way that some data could be partitioned or moved into cold storage then it would be very good.

    For how long have I used the solution?

    We have been using MongoDB for about four and a half years.

    What do I think about the stability of the solution?

    There are bugs in the system but they are not very significant. We have found a workaround for each of those bugs and we have been running the full-scale production cluster for more than four and a half years. As we haven't had any issues, I would say that it is pretty stable.

    This solution is used constantly by both us and our customers, every second of every day.

    We are not looking at increasing our usage. Rather, we will be moving some of our workloads off of MongoDB. Ultimately, usage will be at a standstill or perhaps even reduced.

    What do I think about the scalability of the solution?

    This is a scalable solution. We have close to 100 developers who use it. In addition, our entire business makes use of MongoDB. Everything the customer does makes use of this solution, so I would say that we have at least 100,000 users.

    How are customer service and technical support?

    Because we are using the Community Edition, we don't have any support whatsoever.

    We did interact with them for MongoDB Atlas, and we are still in contact with them to see if we can take something into production a couple of quarters from now.

    Which solution did I use previously and why did I switch?

    We did not use another NoSQL database solution prior to MongoDB.

    How was the initial setup?

    When we installed MongoDB the initial setup was complex. However, now with Atlas, it is very easy. It took us less than a week to deploy and now, with Atlas, there are a lot of things that you don't need to know that was required four years ago.

    What about the implementation team?

    I did the original cluster deployment on my own.

    What's my experience with pricing, setup cost, and licensing?

    We are using the Community Edition of MongoDB. However, we would be happy if the pricing for the full version were more competitive.

    Which other solutions did I evaluate?

    We use a lot of different database products and the choice depends on the use case.

    With respect to NoSQL, we did not evaluate other vendors because when we implemented this solution four and a half years ago, it was the only scalable NoSQL database. This made it a rather obvious choice for us at the time.

    What other advice do I have?

    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.

    Which deployment model are you using for this solution?

    Public Cloud
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Deepak Kumar  T R
    Managing Director at SimSol Technologies And Services Pvt Ltd
    Real User
    Top 20
    Quite scalable, easy to deploy, and affordable
    Pros and Cons
    • "The solution's most important aspect is its seamless database."
    • "The on-premises version of the solution is still pretty expensive, especially compared to the cloud version."

    What is our primary use case?

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

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

    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.

    What do I think about the scalability of the solution?

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

    Which solution did I use previously and why did I switch?

    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.

    How was the initial setup?

    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.

    What about the implementation team?

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

    What's my experience with pricing, setup cost, and licensing?

    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.

    What other advice do I have?

    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.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Learn what your peers think about MongoDB. Get advice and tips from experienced pros sharing their opinions. Updated: January 2022.
    564,143 professionals have used our research since 2012.
    Senior Associate at a financial services firm with 10,001+ employees
    Reseller
    Top 20
    Good for transformation and data storage but quite expensive for smaller organizations
    Pros and Cons
    • "The initial setup isn't really that complex."
    • "MongoDB should better support small and medium companies. There are a lot of clients out there that are interested, however, they need something lighter and less complex and something not so expensive upfront."

    What is our primary use case?

    We primarily use the solution for long-term storage. We use it to store all our data. We also use it to support microservices that already have calculated data. We don't use it for any other purpose.

    What is most valuable?

    The most valuable feature of the solution is the ability to easily store documentation regarding structures. 

    We can easily connect to MongoDB and search without transformation, without joining. If we want to use a simple search it's really fast. 

    The initial setup isn't really that complex.

    The solution is pretty stable overall.

    What needs improvement?

    If we want to perform some joins or some other types of transformation that are more advanced, in that case, we cannot use MongoDB. We need to use another solution.

    The solution needs to better support modern aspects of search engines. There is typically a microservice layer and MongoDB doesn't support well within search engines. If you want to create some complex structures, you need something like Elasticsearch, for example.

    The pricing is expensive.

    MongoDB should better support small and medium companies. There are a lot of clients out there that are interested, however, they need something lighter and less complex and something not so expensive upfront. 

    For how long have I used the solution?

    I've been using the solution for the past two or three years.

    What do I think about the stability of the solution?

    The stability of the solution is very good. There are no bugs or glitches. It doesn't crash or freeze. It's pretty good overall.

    How are customer service and technical support?

    I've never used technical support. I can't speak to their level of responsiveness or how knowledgeable they are.

    Which solution did I use previously and why did I switch?

    We previously mostly used SQL databases. We used Microsoft SQL mostly and we needed some NoSQL databases. That's why we implemented Elasticsearch and MongoDB. We wanted a NoSQL database that we could search, however, was also capable of long-term storage. 

    How was the initial setup?

    The initial setup is not so complex when we are talking about on-prem solutions. It's an easy initial setup. We are fine with that. 

    I was surprised, however, by the lack of support offered during implementation. You are left to your own devices. There isn't much guidance - especially on so complex a transformation.

    What about the implementation team?

    We have our own agent teams. Mostly we rely on our engineers, not consultants at other companies. We're able to handle everything rather well in-house.

    What's my experience with pricing, setup cost, and licensing?

    The pricing is quite high and we don't appreciate the solution raising prices so much.

    I'm following up with the licensing, however, I don't have the exact figures right now. I mostly advise some companies about that, and usually do not go into detail. What I'm interested in, for example, is when you implement some solution in some company what are the costs for that company in the near future, for example, in one or two years. This is what we are thinking about. 

    It's not easy to implement some solutions in some small companies if at the beginning they need to pay some licensing costs upfront. For example, for Mongo DB. It would be easier if the small companies could operate without licensing for some period of time and then only after they grow to a certain size or need they would have to pay some for that usage.

    What other advice do I have?

    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.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: My company has a business relationship with this vendor other than being a customer: Reseller
    Senior DBA & IT Consultant at MA Consulting
    Real User
    Top 5
    A source-available cross-platform document-oriented database that has a useful free edition
    Pros and Cons
    • "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."

    What is our primary use case?

    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.

    What is most valuable?

    I like that MongoDB has a free version. You can also buy the enterprise edition, which is cheaper than Oracle.

    What needs improvement?

    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.

    For how long have I used the solution?

    I've been using MongoDB for two or three years.

    What do I think about the stability of the solution?

    MongoDB isn't stable like Oracle, but it's okay.

    What do I think about the scalability of the solution?

    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.

    How are customer service and support?

    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.

    Which solution did I use previously and why did I switch?

    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.

    How was the initial setup?

    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. 

    What about the implementation team?

    I implemented this solution by myself.

    What's my experience with pricing, setup cost, and licensing?

    MongoDB has a free version. You can also buy the enterprise edition, which is cheaper than Oracle.

    What other advice do I have?

    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.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    Saeed Abedi
    Senior Information Technology Manager at a financial services firm with 51-200 employees
    Real User
    Top 20
    Easy to set up and helpful for storing unstructured data, but the performance could be improved
    Pros and Cons
    • "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."
    • "The performance can be improved."

    What is our primary use case?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

    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.

    What do I think about the scalability of the solution?

    We have not tried to scale our implementation of MongoDB.

    How are customer service and technical support?

    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.

    Which solution did I use previously and why did I switch?

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

    How was the initial setup?

    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.

    What about the implementation team?

    We deployed MongoDB ourselves.

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

    What's my experience with pricing, setup cost, and licensing?

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

    What other advice do I have?

    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.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Data Engineer | Full Stack Developer at a tech services company with 1,001-5,000 employees
    Real User
    A stable solution with schemaless architecture and sharding feature
    Pros and Cons
    • "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."

    What is our primary use case?

    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.

    What is most valuable?

    I like the schemaless architecture that it follows. I also like the sharding that it provides.

    What needs improvement?

    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.

    For how long have I used the solution?

    I have been using this solution for two years.

    What do I think about the stability of the solution?

    It is stable.

    What do I think about the scalability of the solution?

    Currently, we have about 1,000 to 5,000 employees all over India. Most of us are using MongoDB for internal projects. 

    How are customer service and technical support?

    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.

    What other advice do I have?

    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.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Senior Software Engineer at a tech services company with 5,001-10,000 employees
    Real User
    Top 5Leaderboard
    Convenient, scalable, and very easy to use
    Pros and Cons
    • "One of the first things I noticed when I had my first experience with MongoDB was how easy it was to use. I was expecting more difficulties or at least some challenges, but it was very, very easy to use. It's great technology, performs well, and is very convenient."
    • "MongoDB is a very useful and convenient choice, but sometimes for more complex projects, there are certain niche requirements that appear, so using a different tool could be beneficial. It raises the complexity of the architecture, but it could be beneficial to the world, the features, the ease of the features which are being implemented."

    What is our primary use case?

    Our primary use case of MongoDB was development. We used it from a developer point of view, writing the platforms and storing some data. It was deployed on the AWS cloud. 

    What is most valuable?

    One of the first things I noticed when I had my first experience with MongoDB was how easy it was to use. I was expecting more difficulties or at least some challenges, but it was very, very easy to use. It's great technology, performs well, and is very convenient. 

    What needs improvement?

    MongoDB is a very useful and convenient choice, but sometimes for more complex projects, there are certain niche requirements that appear, so using a different tool could be beneficial. It raises the complexity of the architecture, but it could be beneficial to the world, the features, the ease of the features which are being implemented. 

    For how long have I used the solution?

    My experience with MongoDB is pretty recent, maybe for three years. 

    What do I think about the stability of the solution?

    This solution is stable enough. There isn't much maintenance involved—we're just installing some software and then using it—especially since I'm using it from a development point of view. 

    What do I think about the scalability of the solution?

    I've heard that MongoDB is pretty scalable, but we never did any big deployment. I've read a lot about how it scales and can handle huge data. 

    How are customer service and support?

    I have never contacted MongoDB's technical support. 

    How was the initial setup?

    The installation is quite straightforward. I have it installed on my personal laptop and it's very easy to do. It took just a few minutes. 

    There are two or three DevOps guys who are involved with and responsible for all the deployments and setups for the whole project. 

    What about the implementation team?

    I implemented this solution myself. 

    Which other solutions did I evaluate?

    We also considered Cosmos DB. 

    What other advice do I have?

    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

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    Digital General Manager at a tech services company with 10,001+ employees
    Real User
    Good interface and integration with other tools but they should modernize the storage options
    Pros and Cons
    • "I find the integration with other tools very easy."

      What is our primary use case?

      Our primary use case of this solution is for schema lists. It's easy to populate the data and to get information for summaries and things like that. The second use case is that there is a mainframe and the upgrades on the mainframe can use your CPU time. As the customer is working on the mixed product, it becomes very costly. Using MongoDB internally allows us to divide as much as we can with it. And there is a service provision that I think is much cheaper than continuing the maintenance of the machine. 

      What is most valuable?

      The feature I find most valuable, is that it is easy to use. Even a non-technical person will be able to understand it. I also find the integration with other tools very easy.

      What needs improvement?

      The price can always be better. I mean, we are a big corporation so it is quite expensive for us. So perhaps they can improve on the price.

      For how long have I used the solution?

      I have been using MongoDB for two years now.

      What do I think about the stability of the solution?

      MongoDB is very stable.

      What do I think about the scalability of the solution?

      The solution can be scaled without any issues.

      How are customer service and technical support?

      I have not yet contacted the technical support team of MongoDB, but I have great interactions with the MongoDB side. We have our own technical team in our company that takes care of our issues. 

      Which solution did I use previously and why did I switch?

      We have used Snowflake before and I can tell you what the difference is between MongoDB and Snowflake. Snowflake is a totally different type of database. It is basically shot across small units and its solutions are only for the cloud. Your access can be private and it can be fast on the queries. Whereas with MongoDB, it takes much longer than with Snowflake if you want to extract. Snowflake is much faster. It has good analytics capabilities, though.

      How was the initial setup?

      The initial setup was easy and quite fast. The only problem is the provisioning environment within the cloud. Deploying the MongoDB program doesn't take very long. The whole process of deployment needs only one additional person to do its maintenance and to finalize the deployment faster.  

      What other advice do I have?

      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. 

      Which deployment model are you using for this solution?

      On-premises
      Disclosure: My company has a business relationship with this vendor other than being a customer: Partner