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 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.
It's not a specific feature that I value, but the scalability of this system is the most impressive aspect.
The UI should be improved since if you provide the option to query directly when signing into the Azure portal, it makes no sense if you have such a poor UI for querying that you can't even feed the reports correctly.
It should offer a simple user interface for querying Microsoft Azure Cosmos DB.
I have been using Microsoft Azure Cosmos DB for a long time, almost forever.
We are always working with the latest version.
It's fairly stable. I have no complaints about the stability of Microsoft Azure Cosmos DB.
Microsoft Azure Cosmos DB is fully scalable.
Users do not connect to Microsoft Azure Cosmos DB directly. Our APIs connect to Microsoft Azure Cosmos DB and are then used by the front end.
Estimating the number of users is impossible.
Because our complete setup is in Microsoft, we have access to the most premium Microsoft assistance, available 24 hours a day, seven days a week. We have never had a problem with technical support.
The initial setup is straightforward.
The RU's use case determines our license fees. It fluctuates based on how many RUs we have. It's not a fixed-line.
Because our whole solution was hosted on Azure, this was the default option for us. We didn't look into any other possibilities.
I would recommend this solution to others who are interested in using it.
I would rate Microsoft Azure Cosmos DB a seven out of ten.
The company is using Microsoft Azure Cosmos DB for business intelligence information, specifically for demand management.
What I like about Microsoft Azure Cosmos DB is that it's easy to do data ingestion and use the data in different applications. If you talk about business intelligence such as the Power BI tool, it's easy to connect because both are Microsoft products. With Microsoft Azure Cosmos DB, it's easy to connect and do data ingestion.
At the moment, because I'm still new in terms of using Microsoft Azure Cosmos DB, I don't have any feedback regarding areas for improvement in the product. So far, it has met all the expectations and needs of my company.
It would be nice to have more options to ingest the data, for example, more file options or more search options. Currently, you can use JSON, but if there were other file types you can use for data ingestion, that would be nice. This is the additional feature I'd like to see in the next release of Microsoft Azure Cosmos DB.
I've been using Microsoft Azure Cosmos DB for the past six months.
Microsoft Azure Cosmos DB is a stable product.
Microsoft Azure Cosmos DB is a scalable product.
We have a partnership with Microsoft, so the response time of the technical support team for Microsoft Azure Cosmos DB is really good at the moment.
Microsoft Azure Cosmos DB was easy to set up.
I've been using Microsoft Azure Cosmos DB, a cloud DB solution. It's deployed in a cloud environment, on a public cloud with security for ourselves.
My company is a partner of Microsoft and also a reseller.
My advice to people looking into implementing Microsoft Azure Cosmos DB is that it would be good for them to use, specifically if they are looking for a NoSQL database to ingest the data and do data discovery using the data in a BI tool. It's easy to ingest the data and work with the data in Microsoft Azure Cosmos DB and understand that, because it is not a SQL database, which means it's not as structured. You can add data, and then do a data discovery, and use it the best way for you. I would recommend Microsoft Azure Cosmos DB.
My rating for Microsoft Azure Cosmos DB is eight out of ten.
Cosmos is a PaaS, so you don't need to worry about infrastructure and hosting. It has various APIs that allow it to integrate with other solutions. For example, we are using a MongoDB-compatible API for customers, which makes it easier for developers on the team who previously used MongoDB or are accustomed to the old document storage paradigm.
The API compatibility has room for improvement, particularly integration with MongoDB. You have to connect to a specific flavor of MongoDB. We'd also like a richer query capability in line with the latest Mongo features. That is one thing on our wish list. The current version is good enough for our use case, but it could be improved.
We've been using Cosmos DB for about six to eight months.
Cosmos DB's reliability, performance, and scalability are all good. We can't complain. Azure has management outages, and the management windows that Azure publishes are still too big. They provide a 24 hour period in which maintenance will happen. Smaller, specific windows are easier to manage when you have a production system. Otherwise, it does a good job technically.
The scalability of the Azure platform is a given. It's easy to scale and quickly deploy. The API's richness also helped us. We use Cosmos DB for a public-facing application with upwards of a million users.
I think we have all the scalability that we need, and we like that the system doesn't have outages when it's updating. However, an on-prem version is required for some use cases, and they provide this now.
Microsoft support is good if you contact a specialist. Getting in touch with the right specialist is crucial for whatever technology you're using on Azure. If you reach the right person, it's a dream, but that can be difficult in some cases can be difficult. You might go through several layers of support before you reach the platform experts.
We haven't used another solution for this particular use case. The product was benchmarked on Azure, so we used Cosmos DB. It wasn't like we were looking at different solutions, and we chose Cosmos.
Setting up the whole landscape took about a week. It doesn't take long. It's a PaaS, so the setup is mostly configuration. It's more like provisioning rather than deployment. You could probably set it up in a day if you wanted to. We set it up with an in-house team. About 15 to 20 people support the solution, but they aren't dedicated to Cosmos DB. They work on lots of things.
Cosmos DB is a PaaS, so there are no upfront costs for infrastructure. There are only subscriptions you pay for Azure and things like that. But it's a PaaS, so it's a subscription service. The license isn't perpetual, and the cost might seem expensive on its face, but you have to look at the upkeep for infrastructure and what you're saving.
I rate Cosmos DB eight out of 10. I would recommend it for an appropriate use case. However, you need to be aware of the system's limitations. If you're using the DocumentDB system, it's crucial to plan properly for document structure, etc. You also need to plan for failure to ensure that your system can survive when any node fails. Set up clustering, redundancy, high availability, and so on.
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.
Its wide support to the ecosystem is valuable. We can use this database with a lot of use cases, and that's one of the reasons why we prefer it. We have a lot of vendors, databases, and use cases, and wherever possible, we are trying to standardize databases. It is also secure.
At this stage, we would like more enterprise support. We use MongoDB a lot, and we're trying to get rid of MongoDB. So, I would like to see more features in the Cosmos DB API for MongoDB space.
I have been using this solution for almost two years.
It is stable. It has 99.999% availability, and it is backed by SLAs.
We have thousands of users.
We use the cloud version and the on-prem version. We have our on-prem database engineering team. For the cloud, we are okay with their support.
We use MongoDB a lot, and we're trying to get rid of MongoDB.
It is easy to install. I tried it in a testing environment, and it was easy. Database experts should be able to do it easily.
For the cloud, we don't pay for the license, but for the on-prem versions, we do pay.
I would rate Microsoft Azure Cosmos DB a nine out of 10.
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.
There's no specific feature of Cosmos. Basically, we try to query the database. Since it's unstructured data, all the related fields are stored as a single JSON. You don't have to go ahead and hit multiple tables, or multiple containers. Instead, you get all of those things, relationally, stored in a nested JSON — in one single container itself. This way, you don't have to go back and forth to different tables. There are pros and cons with this feature, but often it makes things easier for us.
I am impressed with the TTL (time to live feature) of Cosmos. If we need to perform a manual addition to a container, we just need to configure the time to live. And then based on that, it can be deleted.
We should have more freedom to tweak it and make our own queries for non-traditional use-cases.
I have been using Microsoft Azure Cosmos DB for roughly one year.
Cosmos should be more stable. Sometimes we fetch more than 60,000 records at a time. When we try to fetch large amounts of data, sometimes it breaks-down, requiring us to rescale it. Overall, performance-wise, it needs to be a little more stable.
I personally haven't had contact with the technical support. Our solution architects deal with support.
I wasn't involved in the initial setup. We have a DevOps team that was responsible for handling the installation. We are just leveraging it for developmental purposes.
Cosmos should be cheaper. We actually intend to stop using it in the near future because the price is too high — and because of the stability issues.
Overall, on a scale from one to ten, I would give this solution a rating of seven. Aside from the scalability issues, we haven't experienced any other issues.
I would recommend Cosmos. It made our lives a lot easier. There's not a big learning curve in order to understand the structure and how to use it. We were good to go with only one container. Anybody who is new can learn quickly.
I use the product for storing information related to our automation.
The product is simple to use. It is a NoSQL database. It is easy to commission the environment and use it.
It is not as easy to use as DynamoDB. The product always shows JSON-based documents. However, DynamoDB shows a table-based document. The documentation must be improved.
I used the solution a couple of months ago.
The tool’s stability is very good. I rate the stability a ten out of ten.
The tool is highly scalable. I rate the scalability a ten out of ten. We have more than 1000 users.
I used DynamoDB in my previous organization.
The initial setup is easy. The deployment could be completed within minutes.
The tool is not expensive. It is good for small use cases.
Cosmos DB is a good option if someone is looking for a NoSQL database. Overall, I rate the product a nine out of ten.
We use the product to input data that doesn't require structuring.
Microsoft Azure Cosmos DB's most valuable feature is latency.
The tool's pricing is expensive.
I have been using the product since November 2021.
Microsoft Azure Cosmos DB is stable.
The product is scalable. My company has eight users.
Microsoft Azure Cosmos DB's tech support is okay.
Microsoft Azure Cosmos DB's deployment is straightforward.
Microsoft Azure Cosmos DB's licensing costs are monthly.
I rate the tool a nine out of ten.
We provide automated solutions to manufacturing plants.
The solution is user friendly and Microsoft's technical support is good.
In Microsoft manufacturing, managers really need to know about the product. This market is flooded by other vendors. So putting Microsoft in action in such places looks challenging.
I have been using Microsoft Azure Cosmos DB for four months.
Microsoft Cosmos is stable.
It is a scalable solution and twelve hundred users are using the solution.
The entire POC process and Microsoft's entire page were really smooth. There are no hiccups at all, and the kind of documentation support has really helped to build a competitive customer, so that is good enough.
I rate the overall solution an eight out of ten.
The technical support team is good.
Positive
The initial setup is straightforward. Two developers and one architect were enough for the deployment. The maintenance is easy.
Microsoft provides fair pricing.
If somebody is really looking to adopt a solution like this, this is the best option to go.
I use Microsoft Azure Cosmos DB for some web applications.
The most valuable feature of the solution is that it makes it easy for users to access web applications like Visio while not being complex like AWS at the same time.
The pricing of the solution is an area with certain shortcomings. From an improvement perspective, I wish for the solution to offer users an increased storage capacity at a cheaper price.
I have been using Microsoft Azure Cosmos DB for a few months.
I rate the solution's stability eight to nine out of ten. The solution's stability is good.
It is a scalable solution.
There are almost 1,000 users of the solution in my institution.
The solution is deployed on the cloud.
I think that there was a third-party involvement required during the solution's deployment phase.
Right now, I have opted for the student subscription plan, for which Microsoft charges me around 100 USD. The pricing of the solution depends on the solution's usage.
I recommend the solution to those who plan to use it. It is a cloud-based solution that is easy to deploy, easy to access, and provides users with more features compared to other clouds like AWS and GCP.
I rate the overall solution a nine out of ten.
In our accounting department, we store data in Azure Cosmos DB. We query and store IO-based data there.
I'm still in the process of exploring all the features. We're continuously adding and releasing data, so there are several apps that have been useful to me.
Since we're working in the cloud, it's not easy to incorporate all the features it supports. There is room for improvement in terms of integration with other vendors.
I have been using the solution for about a year.
Cosmos DB is a pretty stable solution. I would rate it a ten out of ten.
The solution is pretty scalable. I would rate the scalability a ten out of ten.
If I had to rate it based on my initial usage, I would rate it around a seven.
The setup was done by the team. They followed a set of instructions and it was pretty straightforward.
I would recommend understanding the underlying databases like Cosmos DB, but I don't think it supports Oracle. However, it does support various other databases. If it supports the databases you need, then go for it. If it doesn't support them, there's not much you can do.
Overall, I would rate the solution an eight out of ten. I'm not giving it a higher rating because it doesn't support all databases.
