There have been some configuration issues, but we haven't hit any thresholds or roadblocks when it comes to throughput. That was one of the reasons that we leaned toward it and not a relational database, especially at scale. We haven't run into any issues when it comes to that.

I had minor issues while using the solution, but they were actively solved, and eventually, a justification was also given. Ninety-five percent of the time I used this solution, there were no issues. Microsoft's service in the cloud market is still growing and so there are some feature limitations. 

The solution is stable. We haven't received news of any issues with platforms.

Stability is rated a nine out of ten. 

Microsoft Azure Cosmos DB is a stable solution if you use it on the Azure cloud.

I rate Microsoft Azure Cosmos DB a nine out of ten for stability.

It offers good stability capabilities.

It is stable. It has 99.999% availability, and it is backed by SLAs.

Microsoft Azure Cosmos DB is a stable solution.

It is a stable solution. I rate the stability a nine out of ten.

The solution is stable. I would give it a five out of five for reliability.

It's fairly stable. I have no complaints about the stability of Microsoft Azure Cosmos DB.

Microsoft Azure Cosmos DB is a stable product.

Microsoft Azure Cosmos DB is a stable solution.

From a stability perspective, it's a pretty robust solution designed to offer high availability and fault tolerance. It provides multiple levels of redundancy and automatic failover to ensure data availability and reliability. 

In my experience, Cosmos DB is definitely stable. But, for any service or application, I wouldn't give it a perfect score. There's always room for improvement. A perfect score would mean no room for improvement. So, I always consider some buffer for improvement.

I would rate the stability a seven out of ten.

I would rate the stability as nine out of ten.

I rate the tool’s stability an eight out of ten.

I would rate stability an eight out of ten. 

It is a stable product. I would give it an eight out of ten. 

Microsoft Azure Cosmos DB is stable. 

I rate Azure Cosmos DB eight out of 10 for stability if you allocate the necessary resource units. It is based on the concept of a resource unit. There are three settings: auto, manual, and another one I can't remember. You can manually set a limit on what goes to the resource unit during a specified time. or it will automatically send and continuously increase. 

This can create some instability. For example, if I limit my resources to 30,000 RUs, I expect to consume, but if the load is higher, it will fail and continue to fail. I will get an error that says, "Too many requests."

If you set it to "auto," you'll have to pay for it. You can adjust the limit, but it will not automatically do it. It requires someone who can think in terms of RUs, not the other databases we usually use. The person should always think in terms of resource units because you're paying for each resource unit. It isn't simply writing queries and pulling the details from the database. That is a steep learning curve. Many assume Cosmos DB is like any other NoSQL or graph DB. 

I rate the solution's stability eight to nine out of ten. The solution's stability is good.

The solution is stable.

The tool’s stability is very good. I rate the stability a ten out of ten.

Microsoft Cosmos is stable. 

This solution is stable. I rarely receive concerns from my clients that they are facing any downtime or that some solutions or configurations are not working.

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. 

Microsoft Azure Cosmos DB is a stable solution.

The solution is stable.

Cosmos DB is a pretty stable solution. I would rate it a ten out of ten. 

Cloud-based solutions like Cosmos DB are quite stable.

It is stable but since we have multiple locations, if one point goes down, we can access another location easily. Most of the effort goes into the script and we use keywords to secure the accessibility and then we set up the encryption. Configuration takes time. We do it without self-script. If you do it manually, it is quite difficult but script does it in a better manner. 

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 solution is stable. There are no bugs or glitches. It doesn't crash or freeze. It's quite reliable.

The stability of Microsoft Azure Cosmos DB was good. I did not experience any bugs or glitches.

The solution is stable.