What is your primary use case for MongoDB?

Our primary use case is mainly for web applications.

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 data storage platform. All our application databases are stored in JSON format, and we also use MongoDB replication.

We primarily use MongoDB as a database to handle large volumes of data. It's useful when we need to manage millions of records quickly.

We use this solution for database verification purposes. Typically, we integrate other analytics tools with the solution, like databases and other tools.

We use MongoDB mainly for data visualization and filtering purposes.

I use MongoDB in our company since our overall data is stored on it. My company uses the tool as a back-end database.

I have used the product to store and manage data operations.

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.

I work with multiple personal applications, and for that, I use MongoDB and SQL Servers. Depending on the use cases, I choose MongoDB, as it is not a heavy application. Usually, I use MongoDB for attachment sections because RDBMS is heavy for attachment software. I also use it for assessments. Sometimes, I store data for a time-series database, such as stock market data, which I analyze using MongoDB.

We use MongoDB for monthly billing of the mobile software we provide to our client, Talent Post. It includes the services they use on their mobile devices.

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.

We use MongoDB to build online applications.

I used the solution in the production level to search data and create education-based tutorials for a project. We had 30 managers, senior architects, tech leads, and software engineers working on the project. Currently, I use the solution for my personal work.

We are using MongoDB for storing user information and our customer data. If an application requires to save information, that data is stored in MongoDB.

We are using MongoDB for unstructured databases.

We do payroll for government workers. One service we provide is called e-Payslip. You go into the portal, create an account, and download your payslip for the month. If you have to do something that requires you to submit a payslip, you can go to the portal and get your payslip electronically. We also have what we call the ESPV. This allows unit managers to validate workers before they are paid for the month. It's an attempt to remove ghost names from the government payroll, so there's a cycle. At some point, somebody who is actually working must be validated in the system, and then the unit head confirms. This is checked by HR before salaries are paid, so you have to be a validated worker before your salary is paid.

We are using MongoDB to store our transactions. On the front end, we developed something in Java, that fits right into the application. We do not use MongoDB's capabilities to do other operations, such as BI.

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.

I'm a developer use it for developing. We develop with it. We use it as a service. We use it in a Docker container.

We do not use MongoDB extensively. Initially, we wanted to store login information, dumping the entire message into the database. It stores transaction details about the users, but only for login purposes. Essentially, we store information about access and usage. In the future, we will build some reports for this data.

We use this solution to deal with large amounts of data, including pictures, voice data, and video data. These types of data are not suitable for SQL databases — MongoDB was designed to deal with such data. Video, pictures, voice, and other files. Currently, we just have one customer using this solution.

We just recently downloading the product and we were trying to do the migration and it worked well. We use it as an individual level only, small projects, and small migrations. We have completed a full project yet.

We use it in our virtual environment. Our software produces a lot of predefined JSON Structures. We save those JSONs in an encrypted form inside MongoDB. It's simple storage of JSON. We do not perform any database functions.

We use it for website designing, and for mobile app designing just like Adobe XD. This is back-end technology that helps in integrating the front end with the back-end systems.

We are using MongoDB as the database on our private cloud, which is AWS in Frankfurt. We monitor different banks adopting cloud in our infrastructure with confirmation and approval by the local regulator. It's mostly all related to our digital part of the bank. We are using MongoDB for the process of onboarding new products. When we are actually calculating proposals for mortgages or complex financial products, we must consider that calculation across many sources. Some are internal. Some are external. We are using MongoDB to support the calculation, or proposal calculation, on our web digital processes.

MongoDB has been installed in our active presentation in Google.

Our primary use case has been for maintaining video content and varying it. We are an enterprise-level organization with around 500,000 employees internationally. The company has over 10,000 users of this solution. I'm an integration solution architect.

We use MongoDB for the applications. You can save two or three applications but there's a lot of people using those applications.

We use MongoDB for big data analysis. We are also developing monitoring tools, and if our data grows big enough, we'll use MongoDB to silo out the data structure.

Our company uses MongoDB for various clients. We primarily use the solution to store the databases, various user logins or log information, and lots of other things.

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.

MongoDB is a database management program that can be used for large data.

I use the solution with an application.

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.

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.