How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.
We use it for our online ERP system.
We are a logistics company, and we have a lot of data coming from the users. We have a model, but we need to be flexible with that model. That is one of the reasons why we are using MongoDB.
We have a lot of mobile apps, and the data of all the mobile users are stored in this database.
We use it for searching. For example, we use some files and documents that are stored in MongoDB, and we use it sometimes to search for certain key words. We also use it to search within the documents that are stored in MongoDB.
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.
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.
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.
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.
We use it for document storage and testing of a proof of concept.
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.
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.
We primarily use the solution as a database. It's basically used as a storage engine.
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.
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.
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.
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.
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.
We use it for big projects. We have multiple DBs on multiple servers, so we have a good performance for it. Sometimes, we are using cloud systems, like Azure, or VMs. We are using MongoDB like a warehouse for data that has no relation nor a need to scale.
I have done a variety of things with MongoDB that started with the adoption of this solution at one company. I was involved in setting up the cluster and then the monitoring, alerting, and backup process. Once all of the set up was complete, I was involved in writing some of the components that were responsible for fetching data from MongoDB. We are now responsible for running the platform, so whoever wants to run MongoDB comes to us and we explain how we can deploy the cluster for their applications. At this point, we build a cluster in the servers under a UNIX account. The number of nodes in the cluster depends on the requirements of the application side. Some of the use cases we have configured MongoDB for are desk-tooling and a payment card profiling project. We are currently working on a data exchange platform. We also have a couple of use cases in the pipeline for potential MongoDB clients who also need the MongoDB Ops Manager.
We used MongoDB to implement a healthcare application into the Amazon Cloud. We deployed that architecture within the South African public health care sector.
We use MongoDB to enable streaming. We have a structured DB where everything is secure. We have everything in folders and structured data. MongoDB is much more better in terms of their response time.
Our primary use case of this solution is to directly monitor public services.
I use it mainly for development. It's a plain document database that maps adjacent data structures. It doesn't cost us that much to integrate. It scales well and it's easy to replicate. It's very easy to set up and it's very easily monitored.
One of the key component of our system uses MongoDB as its data store. We use it for storing data sent by devices. It is an IoT platform.
Is one more resilient than the other?
How supportive are the communities?
Which use cases are better for each?