Cosmos DB has multiple use cases. For instance, we recently developed a custom application for a customer in India. We used Cosmos DB to store data fetched from the initial front end to reduce access times to the application, which is significant for improving user experience. For example, when creating a virtual machine through our custom portal, it is essential to check whether a VM with the same name exists in the same or a different subscription. Additionally, we needed to enforce naming conventions and limitations on the number of VMs that can be created within the same network. These conditional parameters were managed using Cosmos DB, allowing the initial provisioning process to validate data and configurations instantly. This enables us to inform the user right away if there is a duplication or if the creation adheres to predefined rules, offering suggestions based on the UI. This demonstrates the real-time application and benefits of Cosmos DB. We use Cosmos DB for its key-value storage capabilities. For structured data, we always use SQL Database.
In our setup, we rely on Azure Cosmos DB primarily for cloud-native applications that demand global scalability. We use it for connecting web apps and implementing search functionalities.
I use Cosmos DB for geolocation identification. If you pass by a market on the street, it sends me your location. My application will then send you a personalized notification about relevant products you can buy at the market.
Primarily, people do not have a clear understanding of the cloud and cloud services. Customers are a little bit scared about taking their data onto the cloud, and they think and they assume that it is not safe. So we just make them understand that databases or services on the cloud are more secure than on-premises infrastructure.
Microsoft Azure Cosmos DB can be used for various purposes. The query language used for Cosmos DB is very similar to SQL, which gives it an advantage. It's a globally distributed multi-model database service, meaning it supports multiple data models, including documents, key-value pairs, graphs, and time series data models. It's highly scalable and supports consistency, security, and multiple security options, such as REST and transit encryption. It also provides automatic support for these options. These are some top-level benefits of using Cosmos DB, making it a highly versatile and useful tool.
We use Cosmos DB as our entire storage database solution for our application. We don't use any other relational database. We have a file that we use for configuration, but we use Cosmos for user data. We have about 100,000 users a week who visit our website. We have plans to increase usage to four times what we're using now.
We use different Azure services in the development of our solutions. Some of the services we use are Azure Cognitive Services, ADB2C, and SignalR. For most of the solutions, we use a mixture of Azure SQL Database and Cosmos DB. We use Cosmos DB when the data size is huge, and we need to scale. Currently, only two people in my organization are working on this solution: one developer and myself. In the future, I think once the system gets deployed, we will have thousands of users.
We have a massive quantity of data that we need to maintain, and we can't put it in a relational database since we need all of the data and want it to be queried quickly. We maintain it in non-relational databases such as Microsoft Azure Cosmos DB.
We mostly use it for NoSQL use cases. We use it for web applications, mobile applications, and social applications in the financial sector. It is deployed on-premises and on the cloud, and we are using its latest version but not the one in the public review.
Cosmos DB is a non-relational, NoSQL database. We are a solution provider and we implement this product for our clients. It is used for integrating and managing unstructured data such as videos, pictures, and other big objects that you cannot include in a standard database tablet. It is made for these kinds of activities. Some of our customers include banks, where together with their main relational database, it provides a place for keeping track of unstructured data. The relational database is used to store the regular data, whereas Cosmos DB stores what is unstructured. I also use this product for my own purposes.
Associate Manager at a consultancy with 501-1,000 employees
Real User
2021-03-10T07:32:22Z
Mar 10, 2021
We are strict users of Microsoft. We use it to deal with huge amounts of data. It's like Databricks and it's structured. All of the sites we have are stored in Cosmos DB.
Associate Director at a financial services firm with 10,001+ employees
Real User
2021-01-27T12:01:51Z
Jan 27, 2021
We have a database stored on Microsoft Azure where we fetch records and validate them against the application data that is displayed. We use it as a backend in an application to store data. Within our organization, there are around 500 people using this solution.
Cloud Architect at a manufacturing company with 10,001+ employees
Real User
2020-04-30T10:58:00Z
Apr 30, 2020
We have a lot of use cases like for the web API backend where we have most of the processing jobs. It supports mobile, browser, and tablet. We have a single face application that interacts with the users and customers. It's backend and frontend architecture. For middleware, we use Kafka integration. We have PowerBI for reporting.
DocumentDB is a fully managed NoSQL database service built for fast and predictable performance, high availability, elastic scaling, global distribution, and ease of development. As a schema-free NoSQL database, DocumentDB provides rich and familiar SQL query capabilities with consistent low latencies on JSON data - ensuring that 99% of your reads are served under 10 milliseconds and 99% of your writes are served under 15 milliseconds. These unique benefits make DocumentDB a great fit for...
Cosmos DB has multiple use cases. For instance, we recently developed a custom application for a customer in India. We used Cosmos DB to store data fetched from the initial front end to reduce access times to the application, which is significant for improving user experience. For example, when creating a virtual machine through our custom portal, it is essential to check whether a VM with the same name exists in the same or a different subscription. Additionally, we needed to enforce naming conventions and limitations on the number of VMs that can be created within the same network. These conditional parameters were managed using Cosmos DB, allowing the initial provisioning process to validate data and configurations instantly. This enables us to inform the user right away if there is a duplication or if the creation adheres to predefined rules, offering suggestions based on the UI. This demonstrates the real-time application and benefits of Cosmos DB. We use Cosmos DB for its key-value storage capabilities. For structured data, we always use SQL Database.
In our setup, we rely on Azure Cosmos DB primarily for cloud-native applications that demand global scalability. We use it for connecting web apps and implementing search functionalities.
I use the product for storing information related to our automation.
I use Microsoft Azure Cosmos DB for data engineering.
We use Microsoft Azure Cosmos DB for storing information from third-party systems in JSON format.
We handle JSON data and it is compatible with Microsoft Azure Cosmos DB.
I use Cosmos DB for geolocation identification. If you pass by a market on the street, it sends me your location. My application will then send you a personalized notification about relevant products you can buy at the market.
In our accounting department, we store data in Azure Cosmos DB. We query and store IO-based data there.
Primarily, people do not have a clear understanding of the cloud and cloud services. Customers are a little bit scared about taking their data onto the cloud, and they think and they assume that it is not safe. So we just make them understand that databases or services on the cloud are more secure than on-premises infrastructure.
Microsoft Azure Cosmos DB can be used for various purposes. The query language used for Cosmos DB is very similar to SQL, which gives it an advantage. It's a globally distributed multi-model database service, meaning it supports multiple data models, including documents, key-value pairs, graphs, and time series data models. It's highly scalable and supports consistency, security, and multiple security options, such as REST and transit encryption. It also provides automatic support for these options. These are some top-level benefits of using Cosmos DB, making it a highly versatile and useful tool.
We use Cosmos DB as our entire storage database solution for our application. We don't use any other relational database. We have a file that we use for configuration, but we use Cosmos for user data. We have about 100,000 users a week who visit our website. We have plans to increase usage to four times what we're using now.
We use different Azure services in the development of our solutions. Some of the services we use are Azure Cognitive Services, ADB2C, and SignalR. For most of the solutions, we use a mixture of Azure SQL Database and Cosmos DB. We use Cosmos DB when the data size is huge, and we need to scale. Currently, only two people in my organization are working on this solution: one developer and myself. In the future, I think once the system gets deployed, we will have thousands of users.
Our primary use case for this solution is to call confirmation details booked in Cosmos DB.
We have a massive quantity of data that we need to maintain, and we can't put it in a relational database since we need all of the data and want it to be queried quickly. We maintain it in non-relational databases such as Microsoft Azure Cosmos DB.
My current title is that of a Solution Sales Architect.
The company is using Microsoft Azure Cosmos DB for business intelligence information, specifically for demand management.
I was using Microsoft Azure Cosmos DB to correct some performance issues or see more about my environment.
We mostly use it for NoSQL use cases. We use it for web applications, mobile applications, and social applications in the financial sector. It is deployed on-premises and on the cloud, and we are using its latest version but not the one in the public review.
Cosmos DB is a non-relational, NoSQL database. We are a solution provider and we implement this product for our clients. It is used for integrating and managing unstructured data such as videos, pictures, and other big objects that you cannot include in a standard database tablet. It is made for these kinds of activities. Some of our customers include banks, where together with their main relational database, it provides a place for keeping track of unstructured data. The relational database is used to store the regular data, whereas Cosmos DB stores what is unstructured. I also use this product for my own purposes.
We are strict users of Microsoft. We use it to deal with huge amounts of data. It's like Databricks and it's structured. All of the sites we have are stored in Cosmos DB.
We have a database stored on Microsoft Azure where we fetch records and validate them against the application data that is displayed. We use it as a backend in an application to store data. Within our organization, there are around 500 people using this solution.
We have a lot of use cases like for the web API backend where we have most of the processing jobs. It supports mobile, browser, and tablet. We have a single face application that interacts with the users and customers. It's backend and frontend architecture. For middleware, we use Kafka integration. We have PowerBI for reporting.