Cosmos is pretty straightforward. There is more complexity, so you just have to be mindful. We had a small issue with making sure that the disaster recovery settings were set up correctly. We found out that there was some type of outage in the middle of the night, but we noticed that the failover didn't run properly. It was because of some configuration that should have been caught earlier, and it wasn't obvious that we got it wrong.

There are some infrastructure teams that manage some underlying resources that are related to Cosmos and some of the configurations, but for our specific implementation, we have three developers at most. We usually only need two people for maintaining and managing the solution.

Deployment of the solution was very easy. Once the initial numbers are in place based on request units, only the instance creation was a time-consuming process. The time was consumed due to the dependency on other teams like DevOps, who are responsible for provisioning. So, it was a one-time process, but migrating and running the same workload between different environments was not much of a hassle. 

It took less than a week to configure and install this solution. To complete the setup, it took five to six professionals from our team. One key solution architect, two people from the DevOps team, and two solution architects from Microsoft were needed for the deployment of this product.

Maintenance of the solution is very easy because the solution follows a Platform-as-a-Service type of model. There is actually no need for any downtime or a patch upgrade because it is taken care of by Microsoft. I never have to worry about downtime for this solution. They perfectly deliver on the key characteristics of the product. 

The initial setup is simple and straightforward. You can set up a Cosmos DB in a day, even configuring things like availability zones around the world. 

The harder part is on the developer side – designing the collections (similar to tables) and how the data will flow in.

The setup is very easy so I rate it a nine out of ten. 

In the initial days in 2018, setup was uncertain and coding was needed from our side. Now, we use the library to access the database or read and write. Things become so much easier over time. 

The solution's initial setup is straightforward if you use it on the Azure cloud.

The initial setup presented some challenges and required us to delve deeper into understanding the daily implications. Microsoft documentation proved to be a valuable resource in navigating this process.

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.

The solution's initial setup is straightforward.

The solution's initial setup is easy. The deployment took almost one day. We migrated the services from the CRM system, converted them into JSON, and deployed it. I would rate the initial setup an eight out of ten. 

The initial setup depends on the type of setup you require. You have to design it properly. The architects need to do some homework to ensure the purpose and the requirements are clear. There are many design decisions that must be made first. Once those decisions are made, the initial setup is quite easy. 

Deployment of the solution was completed within a week.

Overall, I would give the solution a four out of five for ease of setup.

The initial setup is straightforward.

Microsoft Azure Cosmos DB was easy to set up.

We use Terraform scripts for the initial setup of the solution, which doesn't take much time.

There is some learning curve associated with this software. It becomes relatively easy to implement if you have an expert to work with. 

The deployment process and maintenance depend on the size of the product and what you're trying to migrate. Generally, one cloud solution architect and one big data developer with Azure experience should be sufficient.

If you're familiar with it, it's not complex at all. But for someone new, it can be a little tricky.

Cosmos DB itself is a cloud-based solution. However, I'm currently working primarily with a hybrid solution: Azure Stack HCI with software-defined networking for the environment.

It's very easy to set up Cosmos DB. First, you decide what type of API to use, like SQL, Graph, etc., or if you want support for MongoDB or Cassandra APIs. I usually use SQL API. Once you choose the type of API, you create an account and a database. Then you create containers, and you can easily write queries.

It is a cloud-only solution.

The initial setup is straightforward. It's very easy to start a function or application with Azure. 

The initial setup was difficult. I would give it a six or seven out of ten.

Microsoft Azure Cosmos DB's deployment is straightforward. 

I rate Cosmos DB nine out of 10 for ease of setup. The setup is easy, but backing Cosmos DB takes a little more work. It isn't difficult, but you have to raise a request to Azure support. It isn't in your control. The documentation is good enough that most application developers can handle it by following the steps in the documents.

We did it in-house. Two developers should be more than enough. One person could do it alone, but it's always good to have an extra person to verify that your actions are correct. After deployment, it doesn't require any maintenance. When you want to make a copy, you submit a request to the support team and within 24 hours. 

The solution is deployed on the cloud.

The initial setup is straightforward. We deploy Cosmos DB once or twice a quarter. We have three or four teams handling deployment and maintenance, which is about 38 members.

The initial setup is easy. The deployment could be completed within minutes.

The initial setup is straightforward. Two developers and one architect were enough for the deployment. The maintenance is easy. 

The initial setup of Microsoft Azure Cosmos DB is straightforward.

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.

The initial setup is straightforward and needs a few tools to upload.

The setup for this solution isn't complex.

If I had to rate it based on my initial usage, I would rate it around a seven.

The initial setup is straightforward. It was complete in about five minutes.

It takes time to set up and understand. Since Azure has its own table, it's not so flexible. 

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. 

The installation is not complex. It's very straightforward and very easy. It hardly takes more than a few minutes to deploy the product. Everything happens very fast.

It is an easy-to-set-up and maintain product. The installation process involves integrating it into the pipeline. It takes a few minutes to an hour and requires five executives to implement it.

Microsoft Azure Cosmos DB was relatively easy to set up.

The initial setup is straightforward and can be done in a couple of hours.